Skip to content
major vulnerability· requires attention

Remote, no-user-interaction use-after-free in Android that can yield system/root escalation on widely deployed mobile devices; high potential for device takeover.

Mobile

CVE-2026-56960

9.8
Critical
EPSS n/aPatch availableSep 17, 2026

Remote use-after-free in Android enabling privilege escalation without user interaction

common questions

Is CVE-2026-56960 being exploited?

Not confirmed. CVE-2026-56960 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.

How severe is CVE-2026-56960?

CVE-2026-56960 is rated Critical with a CVSS score of 9.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-56960?

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

What does CVE-2026-56960 affect?

CVE-2026-56960 affects Google Pixel devices (Android - Sept 2026 bulletin), Android OS components (framework/native). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-56960?

Install Android Sept 2026 security update immediately; isolate unpatched devices

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

executive summary
technical analysis
affected
Google Pixel devices (Android - Sept 2026 bulletin)Android OS components (framework/native)
impact

Remote attacker can trigger UAF to escalate to system/root, enabling full device takeover, data access, and persistence.

action required

Immediate action required

affected versions
Google Android
  • affectedAndroid kernel

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