Google Android: Race condition allows coprocessor firmware modification
Summary
A race condition in multiple locations allows authenticated coprocessor firmware in shared memory to be modified before it is loaded. An attacker who already has System-level execution privileges on a device can use this to escalate privileges locally. No user interaction is needed, but the attack requires an existing foothold on the device.
Affected
- Google Android on affected Pixel devices (Pixel Update Bulletin, November 2026)
- Exact affected component: unconfirmed. The CVE record names the Android kernel; the bulletin lists the subcomponent as Bootloader.
- Affected patch levels before 2026-11-05 (exact version range unknown)
Fixed in
- Security patch level 2026-11-05 or later, per Google's Pixel Update Bulletin
- Fixed build numbers for this CVE: unknown
- Rollout timing is reported inconsistently; check each device's patch level directly
- Pixel 6 and Pixel 6 Pro may no longer receive updates after October 2026; this is unverified
Workaround
Unknown. No vendor-published workaround was found. Installing the 2026-11-05 patch level is the practical mitigation.
Exploitation
- No evidence of exploitation in the wild found; one aggregator lists KEV as "No", which is not an authoritative CISA check
- No public proof of concept found
- CISA SSVC assessment: Exploitation none, Automatable no, Technical Impact total
Our recommendation
- Confirm that all managed Pixel devices have security patch level 2026-11-05 or later
- Identify devices that no longer receive security updates and plan their replacement or isolation
- Verify the KEV status against the CISA catalogue
- Treat this as a privilege-escalation step; the CVSS score is 6.4 (MEDIUM), but Google rates it Critical, so do not underestimate it
- Apply the monthly update cycle, as this bulletin contains many other critical fixes
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Pixel Update Bulletin November 2026 source.android.com
- CVE Record CVE-2026-56949 www.cve.org
- OSV entry PUB-A-511823474 osv.dev
- Strix CVE-2026-56949 www.strix.ai
- Google Pixel November 2026 update rollout (Jetstream) jetstream.blog
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 13:45.
Original description (NVD)
In multiple locations, there is a possible way to modify authenticated coprocessor firmware in shared memory before loading due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
NVD references (1)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.