CVE-2026-33854
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 · uneditedOut-of-bounds Write vulnerability in MolotovCherry Android-ImageMagick7.This issue affects Android-ImageMagick7: before 7.1.2-10.
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 · moderate confidenceOut-of-bounds Write vulnerability in MolotovCherry Android-ImageMagick7 library versions prior to 7.1.2-10. The vulnerability allows writing data beyond allocated buffer boundaries during image processing operations, which could lead to memory corruption and potential remote code execution when processing maliciously crafted image files.
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-10CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify the installed Android-ImageMagick7 versionCheck your app's dependency manifest (build.gradle, gradle.lock, or libs.versions.toml) for 'imagemagick7' or 'Android-ImageMagick7' and note the declared version number. If using a bundled .so library, inspect the library filename or metadata for version strings.Affected if The declared or bundled version is earlier than 7.1.2-10 (e.g., 7.1.2-9, 7.1.1-x, 7.0.x, or any version without the -10 suffix).
-
Locate the ImageMagick library in the deployed applicationIf you have access to the built APK, extract it and search for libMagick*, ImageMagick*, or magick* files in the lib/ directory. Note the exact file names and any version indicators within.Affected if The library files are present in the APK and the version cannot be determined or is confirmed below 7.1.2-10.
-
Verify image processing code paths that use the librarySearch your codebase for calls to ImageMagick/C++ API functions that perform image encoding, decoding, or transformation (e.g., MagickReadImage, MagickWriteImage, MagickResizeImage). Identify which code paths handle external or untrusted image input.Affected if Your application processes images using the Android-ImageMagick7 library, especially when handling user-supplied or network-received image files.
You are affected if your deployed application bundles Android-ImageMagick7 version lower than 7.1.2-10 AND your code uses the library to process image data.
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-10
Upgrade Android-ImageMagick7 to version 7.1.2-10 or later to obtain the security patch for this vulnerability.
7.1.2-10
- 1. Identify the current version of Android ImageMagick7 in your Android project by checking build.gradle or equivalent dependency configuration
- 2. Update the dependency version for Android ImageMagick7 from the current version to version 7.1.2-10
- 3. Run a build to verify the dependency resolves correctly
- 4. Test the image processing functionality that uses ImageMagick to ensure the upgrade does not introduce regressions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33854 — 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-33854 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