# CVE-2026-58984: CVE-2026-58984

Status: published. Published: 2026-11-02. Updated: 2026-11-02.

In multiple locations, there is a possible memory corruption due to a use-after-free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Google / Android: 17 (affected); 16-qpr2 (affected); 16 (affected); 15 (affected). Source: CNA: google_android

## Severity and prioritization

- CVSS 3.1: 8.4 (high); CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; source: ADP: CISA-ADP

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-416

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://source.android.com/docs/security/bulletin/2026/2026-11-01 (CNA: google_android)

## Provenance

- CNA: google_android: https://www.cve.org/CVERecord?id=CVE-2026-58984; retrieved 2026-11-02; source updated 2026-11-02

Revision: 906e7ed55578131ec7794406e3a1ac8299b14156fc39a7fe0aa61728a280a664

Canonical: https://y2.dev/cve/CVE-2026-58984

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.