Read the docs

Missing bounds check in Google Android allows zeroing secure memory

Priority LOW 30CWE-119Published · Updated

Key facts

Attack vector
Local
Privileges required
High
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-119 and the CVSS impact.

Summary

Google Android is affected, with the Android kernel listed as the affected component. A missing bounds check (CWE-119) lets unvalidated image body addresses zero arbitrary secure memory. A local attacker with high privileges and System execution privileges can cause physical escalation of privilege, and no user interaction is needed.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

In multiple locations, there is a possible way to zero arbitrary secure memory via unvalidated image body addresses due to a missing bounds check. This could lead to physical escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00084 0th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GoogleAndroidAndroid kernel—No fix listedCNA
  • Android VendorGoogle Affected Android kernel Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:o:google:android:*:*:*:*:*:*:*:*——Google
  • cpe:2.3:o:google:android:*:*:*:*:*:*:*:* Versions — — ·Google

Remediation

The sources list no fixed version for Google Android.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-58805
  2. 2026-11-10 Alias added: GHSA-xpqv-p5cr-3wgr
  3. 2026-11-13 CVSS score added · CISA ADP
  4. 2026-11-13 Weakness changed · CISA ADP
  5. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2025-09686 Type confusion in V8 in Google Chrome allows heap corruption KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-07390 Type confusion in V8 in Google Chrome allows heap corruption KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04898 Type confusion in V8 in Google Chrome allows sandbox code execution KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04600 Type confusion in Google Chrome V8 lets attackers run code KEVCVSS 3.1CRITICAL 9.6
  • TI-2024-04346 Use after free in Google Chrome Visuals component KEVCVSS 3.1CRITICAL 9.6
  • TI-2023-05824 Integer overflow in Skia in Google Chrome enables sandbox escape KEVCVSS 3.1CRITICAL 9.6
See all 17497 →

Sources