Skip to content
major vulnerability· requires attention

Android OS media framework flaw enables remote privilege escalation/DoS across many devices; impacts enterprise mobile fleets and is widely deployed.

Mobile

CVE-2026-28666

8.8
High
EPSS 0.29%Patch availableSep 11, 2026

Android LocalImageResolver DNG bypass enables remote DoS and privilege escalation

common questions

Is CVE-2026-28666 being exploited?

Not confirmed. CVE-2026-28666 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.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-28666?

CVE-2026-28666 is rated High with a CVSS score of 8.8. 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-28666?

Yes. A fix has been recorded for CVE-2026-28666. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-28666 affect?

CVE-2026-28666 affects Android OS (media framework - LocalImageResolver), Android devices (Pixel and OEM devices). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-28666?

Apply Android security updates immediately; restrict untrusted image handling

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Android OS (media framework - LocalImageResolver)Android devices (Pixel and OEM devices)
impact

Remote crafted DNG bypass causes persistent DoS and allows privilege escalation on Android via LocalImageResolver, no user interaction required.

action required

Immediate action required

affected versions
Google Android
  • affected17
  • affected16-qpr2
  • affected16
  • affected15
  • affected14

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free