CVE-2026-46557
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-23, due to a missing depth check a stack overflow can occur in the fx operation by passing a crafted argument. This issue has been patched in version 7.1.2-23.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImageMagick versions prior to 7.1.2-23 contain a stack overflow vulnerability in the fx operation due to a missing depth check. Attackers can trigger the overflow by providing a crafted argument to the fx function, potentially leading to application instability or denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.1.2-23CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if ImageMagick is installed and get the version numberRun 'identify -version' or 'convert -version' to retrieve the installed ImageMagick versionAffected if The version displayed is less than 7.1.2-23
-
Confirm the fx operation is available in your ImageMagick installationRun 'convert -list configure | grep -i fx' or attempt a basic fx operation like 'convert -size 10x10 xc:red -fx "u" output.png'Affected if The fx operation executes without error, indicating the vulnerable feature is present
-
Verify the depth-related parameter handling in fx operations (optional advanced check)Review ImageMagick delegate policies in /etc/ImageMagick-6/policy.xml or /etc/ImageMagick/policy.xml if available, looking for any restrictions on the fx delegateAffected if No policy restrictions exist on the fx operation and the version is below 7.1.2-23
You are affected if ImageMagick is installed with a version lower than 7.1.2-23 and the fx operation is available and enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.1.2-23
Upgrade ImageMagick to version 7.1.2-23 or later, which includes the proper depth check to prevent the stack overflow.
ImageMagick 7.1.2-23 or later
- Check current ImageMagick version using 'convert -version' or 'magick -version'
- Update your system's package repository metadata
- Upgrade ImageMagick using your system's package manager (e.g., 'apt-get update && apt-get install imagemagick' for Debian/Ubuntu, 'yum update ImageMagick' for RHEL/CentOS, or 'brew upgrade imagemagick' for macOS)
- Verify the installed version is 7.1.2-23 or later using 'convert -version'
- Test that critical image processing workflows function correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46557 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data