CVE Intelligence
Low Memory corruption

CVE-2026-119124 — ImageMagick before 7.1.2-34 Heap Buffer Overflow via -morph Option

ImageMagick before 7.1.2-34 contains a heap-based buffer overflow in its -morph processing, where crafted images cause writes beyond the bounds of a heap buffer. An attacker can supply a crafted image that, when processed by a user with the -morph option, corrupts heap memory and crashes the application.

Published Oct 29, 2026 · Updated Oct 30, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • No scoring signals.

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Imagemagick
Imagemagick
CVSS base
3.3
Low · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Imagemagick Imagemagick).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Imagemagick Imagemagick < 7.1.2-34 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.8 CVSS 4.0 Medium — — disclosure@vulncheck.com via NIST National Vulnerability Database
4.8 CVSS 4.0 Medium — — VulnCheck via CVE Program (cve.org) e CISA ADP
3.3 CVSS 3.1 Low 1.8 1.4 disclosure@vulncheck.com via NIST National Vulnerability Database
3.3 CVSS 3.1 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-122 · Heap-based Buffer Overflow

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Awaiting Analysis → Undergoing Analysis
    Oct 30, 2026 · NIST National Vulnerability Database
  • Affected products added · imagemagick/imagemagick
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 29, 2026
  • CVSS changed · 3.3
    Oct 29, 2026 · NIST National Vulnerability Database
  • Source status changed · → Awaiting Analysis
    Oct 29, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 29, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 29, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 29, 2026 – Oct 29, 2026

References

2 on the record

Elsewhere on this site

Imagemagick
every CVE for this vendor
CWE-122
other pages naming this weakness

Related CVEs (same products)

  • Low CVE-2026-119123 ImageMagick before 7.1.2-34 Stack Overflow in TIFF Decoder 1d
  • Low CVE-2026-116157 ImageMagick before 7.1.2-33 Memory Leak in PerlMagick Property Reading 5d
  • Low CVE-2026-116156 ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Memory Leak via -set profile Option 5d
  • Low CVE-2026-116159 ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Memory Leak via -cdl Option 5d
  • Low CVE-2026-116158 ImageMagick before 7.1.2-33 Memory Leak in magick compare 5d
  • Low CVE-2026-116160 ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Heap Buffer Overflow via X11 Animate 5d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-119124 is "ImageMagick before 7.1.2-34 Heap Buffer Overflow via -morph Option", rated Low. It affects Imagemagick (Imagemagick); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.3 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.