CVE-2025-53019
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. In versions prior to 7.1.2-0 and 6.9.13-26, in ImageMagick's `magick stream` command, specifying multiple consecutive `%d` format specifiers in a filename template causes a memory leak. Versions 7.1.2-0 and 6.9.13-26 fix the issue.
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-0 and 6.9.13-26 contain a memory leak in the `magick stream` command. When multiple consecutive `%d` format specifiers are used in a filename template (e.g., `output%d%d.png`), memory is allocated but not properly freed, leading to resource exhaustion.
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< 6.9.13-26>= 7.0.0-0, < 7.1.2-0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 ImageMagick versionRun `magick -version` or `identify -version` to determine the installed versionAffected if Version is less than 6.9.13-26, or is 7.0.x less than 7.1.2-0
-
Find magick stream command usageSearch scripts, cron jobs, or application code for invocations of the `magick stream` commandAffected if The magick stream command is actively used in the environment
-
Inspect output filename templatesReview any magick stream command arguments that specify output file paths, looking for patterns containing multiple consecutive %d format specifiers such as output%d%d.pngAffected if The output filename template contains two or more %d specifiers directly adjacent to each other
User is affected only if running a vulnerable ImageMagick version AND using magick stream with consecutive %d format specifiers in the output filename template
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 · scoped6.9.13-267.1.2-0
Upgrade ImageMagick to version 7.1.2-0, 6.9.13-26, or later. Avoid using consecutive `%d` format specifiers in `magick stream` filename templates as a temporary workaround until patching is possible.
ImageMagick 6.9.13-26 (for 6.x branch) or ImageMagick 7.1.2-0 (for 7.x branch)
- 1. Check current ImageMagick version by running 'magick -version' or 'identify -version'
- 2. If using ImageMagick 6.x branch (versions below 6.9.13-26), upgrade to version 6.9.13-26 or later
- 3. If using ImageMagick 7.x branch (versions 7.0.0-0 through 7.1.1-x), upgrade to version 7.1.2-0 or later
- 4. Verify the upgrade was successful by running 'magick -version' and confirming the installed version matches or exceeds the fixed release
- 5. Test the 'magick stream' command functionality to ensure normal operation after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53019 — 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-2025-53019 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