In is_valid_header of timed_cache_item.c, there is a possible out-of-bounds write due to a missing bounds check.
Affects AOSP version 17's System component at the 2026-11-01 patch level. The listed fix is in AOSP version 17.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 17
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects AOSP version 17 (System component, 2026-11-01 patch level).
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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? →
- 5/100 · provisional
- 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? →
- Specific setups only
- Fix
- Fixed in 17
- 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
Summary
This vulnerability affects an Android component that handles timed cache items, where a missing bounds check can allow data to be written past the end of a buffer. A local attacker could exploit this to escalate privileges on the affected device without requiring user interaction.
Read the original description
In is_valid_header of timed_cache_item.c, there is a possible out-of-bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
What to do
Check whether your setup matches what the bug needs.
Affects AOSP version 17 (System component, 2026-11-01 patch level).Upgrade to a fixed version: 17.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Google Android
17
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-58977
What does this mean?
A missing bounds check in is_valid_header in timed_cache_item.c allows an out-of-bounds write. A local attacker could use it to escalate privileges to System execution privileges.Source: source.android.com
Am I affected, and how do I check?
The bug is listed for AOSP version 17, System component, at the 2026-11-01 patch level. To check a device, compare its AOSP version and security patch level with these values.Source: source.android.com
What should I do about it?
Update to AOSP version 17 with the 2026-11-01 patch level, which is the listed fix. No workaround is listed.Source: source.android.com
Is it 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