In has_booted_successfully of sys_state_setup_otp_ta.c, there is a possible way to trigger a permanent denial of
Source GCVE Database
Not known to be exploited.
Data as of 10 Nov 2026, 23:03 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 10 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 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GoogleAndroid | Affected
| Fixed in– |
Description
A logic error in the has_booted_successfully function of sys_state_setup_otp_ta.c can cause premature anti-rollback fuse updates, potentially triggering a permanent local denial of service. Exploitation does not require user interaction or additional privileges.