CVE-2026-59048: In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check
Source GCVE Database
Not known to be exploited.
Data as of 2 Nov 2026, 22:30 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
Description
CVE-2026-59048 is a vulnerability in the rb_cpu_init function of trace.c involving a possible out-of-bounds read caused by an incorrect bounds check. This flaw can lead to local information disclosure without requiring additional execution privileges or user interaction.
References
- nvd.nist.gov/vuln/detail/CVE-2026-59048 (opens in a new tab)
- android.googlesource.com/kernel/common/+/5e31aa53a963b254ddac8a88b48e5b64cfc38eea (opens in a new tab)
- android.googlesource.com/kernel/common/+/e46b3a946c957ab463a8abf9333dea702e8a485e (opens in a new tab)
- source.android.com/docs/security/bulletin/2026/2026-11-01 (opens in a new tab)