VulnerabilityPublished 24 Mar 2026

CVE-2026-33855: MolotovCherry Android-ImageMagick7 · Integer Overflow or Wraparound

Affects MolotovCherry Android-ImageMagick7Source CVE Database V5

Not known to be exploited · CVSS 5.5 Medium : upgrade to 7.1.2-11 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.1.2-11

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade molotovcherry/Android-ImageMagick7 and Android-ImageMagick7 to 7.1.2-11.

Affected software

Product	Affected	Fixed in
MolotovCherryAndroid-ImageMagick7	Affected <7.1.2-11	Fixed in–
GitHubmolotovcherry/Android-ImageMagick7`pkg:github/molotovcherry/Android-ImageMagick7`Other threats	Affected <7.1.2-11	Fixed in 7.1.2-11
GitHubAndroid-ImageMagick7`pkg:github/Android-ImageMagick7`Other threats	Affected <7.1.2-11	Fixed in 7.1.2-11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-33855, organizations should: 1) Monitor for and apply updates to Android-ImageMagick7, specifically upgrading to version 7.1.2-11 or later once released. 2) Implement strict input validation and sanitization for image files processed by the application to reduce the risk of triggering the overflow. 3) Restrict local access to devices and enforce least privilege principles to limit potential attackers' ability to interact with vulnerable components. 4) Educate users about the risks of opening untrusted or unsolicited image files to reduce the likelihood of user interaction-based exploitation. 5) Employ application sandboxing and runtime protections on Android devices to contain crashes and prevent system-wide impact. 6) Monitor logs and system behavior for signs of crashes or abnormal application terminations related to image processing. 7) Consider deploying host-based intrusion detection systems that can detect anomalous behavior indicative of exploitation attempts. These steps go beyond generic patching advice by emphasizing proactive input validation, user awareness, and layered defense strategies to reduce exploitation risk before patches are applied.

Description

Integer Overflow or Wraparound vulnerability in MolotovCherry Android-ImageMagick7.This issue affects Android-ImageMagick7: before 7.1.2-11.

Impact

The primary impact of CVE-2026-33855 is a denial of service condition affecting availability. For organizations, this can translate into application crashes or system instability when processing specially crafted images, potentially disrupting business operations that depend on image manipulation or rendering. While confidentiality and integrity are not directly affected, the loss of availability can hinder productivity, especially in sectors such as media, telecommunications, and mobile services where image processing is critical. The local attack vector and requirement for user interaction limit the scope of exploitation, reducing the likelihood of widespread automated attacks. However, targeted attacks against high-value devices or users could still cause significant disruption. Enterprises with large Android device fleets or those embedding Android-ImageMagick7 in their applications should be aware of potential service interruptions. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits once the vulnerability details are widely known.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/MolotovCherry/Android-ImageMagick7/pull/187 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 18:48 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats