Raw vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-33900 is a medium-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Imagemagick Imagemagick. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 36th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33900 is an integer truncation/wraparound vulnerability (CWE-190) in the viff encoder of ImageMagick, a free and open-source software suite for editing and manipulating digital images. The flaw affects 32-bit builds of ImageMagick versions below 7.1.2-19 and 6.9.13-44, where it can trigger an out-of-bounds heap write, potentially leading to a crash. The vulnerability carries a CVSS v3.1 base score of 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H), indicating medium severity primarily due to its availability impact.
A remote, unauthenticated attacker could exploit this vulnerability over the network by supplying a specially crafted image file that exercises the viff encoder on a vulnerable 32-bit ImageMagick installation. Exploitation requires high attack complexity, with no user interaction needed, but results solely in denial-of-service through application crashes via the heap overflow; no confidentiality or integrity impacts are possible.
ImageMagick has addressed the issue in versions 6.9.13-44 and 7.1.2-19, as detailed in the project's security advisory (GHSA-v67w-737x-v2c9) and corresponding GitHub commit (d27b840a61b322419a66d0d192ff56d52498148d). Security practitioners should update to these patched releases; a related update is available in Magick.NET version 14.12.0. The vulnerability was published on 2026-04-13.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-22102
Vulnerability Data
ImageMagick is free and open-source software used for editing and manipulating digital images. In versions below both 7.1.2-19 and 6.9.13-44, the viff encoder contains an integer truncation/wraparound issue on 32-bit builds that could trigger an out of bounds heap write,…
more
potentially causing a crash. This issue has been fixed in versions 6.9.13-44 and 7.1.2-19.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Input validation enforces bounds on values before arithmetic, stopping the conditions that trigger overflow or wraparound.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.