Cyber Resilience

CVE-2026-33854

Memory Safety in Molotovcherry Android-Imagemagick7 ≤ 7.1.2-10

Memory Safety
Published
24 March 2026
Modified
26 March 2026
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0024 16th percentile
Risk Priority 62 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-33854 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Molotovcherry Android-Imagemagick7. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 16th 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-15 (Development Process, Standards, and Tools) — 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-33854 is an out-of-bounds write vulnerability (CWE-787) in the MolotovCherry Android-ImageMagick7 library. It affects versions of Android-ImageMagick7 prior to 7.1.2-10. The vulnerability was published on 2026-03-24 and carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact.

The vulnerability can be exploited over the network by an unauthenticated attacker with low complexity, though it requires user interaction, such as processing a specially crafted image file. Successful exploitation enables high-impact consequences, including unauthorized disclosure of information, modification of data, and denial of service, potentially leading to full system compromise on affected Android devices using the vulnerable ImageMagick implementation.

A pull request addressing the issue is available at https://github.com/MolotovCherry/Android-ImageMagick7/pull/184, which security practitioners should review for patching details and apply the fix by upgrading to Android-ImageMagick7 version 7.1.2-10 or later.

EU & UK References

Vulnerability Data

Out-of-bounds Write vulnerability in MolotovCherry Android-ImageMagick7.This issue affects Android-ImageMagick7: before 7.1.2-10.

CWE(s)
CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-20023Shared CWE-787
CVE-2024-9468Shared CWE-787
CVE-2024-11517Shared CWE-787
CVE-2024-7352Shared CWE-787
CVE-2023-43866Shared CWE-787
CVE-2024-27376Shared CWE-787
CVE-2023-43196Shared CWE-787
CVE-2023-46257Shared CWE-787
CVE-2024-26815Shared CWE-787
CVE-2023-42566Shared CWE-787

Affected Assets

molotovcherry
android-imagemagick7
≤ 7.1.2-10

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SI-10 Information Input Validation partial match

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

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.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

PR.PS-06 partial match
prevents

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

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.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory handling.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References