In multiple locations, there is a possible memory safety issue due to a use-after-free.
Affects Google Android across versions with no specified ranges; CVSS scores it 9.8 critical. Fixed in security patch level 2026-11-05 or later.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026-11-05
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2026-11-05.
- Last modified
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.31% · 23rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2026-11-05.
Timeline
- CVE published
- First seen by cve.now2 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- Posted on X by cve.now
Affected versions
- Google Android
17, 16-qpr2, 16, 15, 14
On X 8
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58876
Is CVE-2026-58876 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A use-after-free memory safety issue in several places in Android can let an attacker run code remotely, with no extra execution privileges needed. The advisory describes the impact as remote code execution.Source: source.android.com
Which versions are affected by CVE-2026-58876?
Android: versions 17, 16-qpr2, 16, 15, 14.Source: cve.now feed data
Am I affected, and how do I check?
The facts do not list specific Android versions or setups as affected. To check a device, open Settings and look at the security patch level under About phone or Software information.Source: source.android.com
How do I fix CVE-2026-58876?
Install the security patch level 2026-11-05 or later, which the advisory says addresses all of these issues. Check for system updates in Settings.Source: source.android.com