CVE-2026-21045
Out-of-bounds write in TIFF parser allowing remote memory corruption on affected devices
Is CVE-2026-21045 being exploited?
Not confirmed. CVE-2026-21045 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-21045?
CVE-2026-21045 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-21045?
Yes. A fix has been recorded for CVE-2026-21045. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-21045 affect?
CVE-2026-21045 affects libimagecodec.media.quram.so, Android devices with affected Qualcomm image codec, OEM devices prior to SMR Jul-2026 Release 1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-21045?
Apply SMR Jul-2026 Release 1 or vendor patch; block/unpack untrusted TIFFs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote crafted TIFF can trigger out-of-bounds write leading to memory corruption, crashes, or potential remote code execution.
Patch when possible