Google Android privilege escalation via out-of-bounds write in gscan.cpp
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Summary
A missing bounds check in the event handling code of gscan.cpp allows an out-of-bounds write on the heap, which could let an attacker escalate privileges. Exploitation does not require user interaction.
Written by a model
Original description
In handleEvent of gscan.cpp, there is a possible way to trigger an out of bounds write on the heap due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-58705 (In handleEvent of gscan.cpp, there is a possible way to trigger an out of bounds write on the heap due to a missing bounds check.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-58705 (entry last updated 2026-11-13):
Affected:
- Google Android: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-58705 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-58705 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://source.android.com/docs/security/bulletin/pixel/2026/2026-11-01
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-58705
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-58705"}.Affected versions
- Google AndroidVersion range not reported
cve.now Index
- Exploitation0/40No signal
- Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 40 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now2 days
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Posted on X by cve.now1 day
- Record last updated
Public exploit activity
- EPSS: 0.39%
- Posted on X by cve.now Nov 12
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | source.android.com · docs/security/bulletin/pixel/2026/2026-11-01 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-58705 |
| Record | NVD · CVE-2026-58705 |
Related
- CVE-2026-59626In SendInfo of UssiController.cpp, there is a possible way to corrupt memory via a dangling connection listener pointer due to a use after…
- CVE-2026-59625In GetTwiddledMiptreeSparsePageMap of texmgmt.c, there is a possible way to trigger an out of bounds write due to a logic error.
- CVE-2026-95405In acquireMemory of bt_bqr_offload.cc, there is a possible way to trigger an out of bounds write via a buffer size underflow due to an…
- CVE-2026-95403In multiple locations, there is a possible way to trigger an out of bounds write in the shared memory tracking bitmap due to a missing…
- CVE-2026-95400In StNfc_hal_write of hal_st21nfc.cc, there is a possible way to trigger an out of bounds write into global memory due to an incorrect…
- CVE-2026-59630In check_constraint_monotonicity of lib.rs, there is a possible way to downgrade stored security policies and bypass rollback protection…
No corrections so far. Something wrong on this page? Report an error.