Improper authentication in Android
Key facts
- Attack vector
- Physical
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- 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-287.
Summary
In (TBD) of (TBD), there is a possible way to bypass the lockscreen due to Biometric Auth Failure. This could lead to local escalation of privilege with physical access to the device with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-240428519References: N/A
Why it matters now
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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | Android | Android kernel | — | No fix listed | CNA |
- Android Vendor— Affected Android kernel Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2023-20924
- 2026-10-03 Alias added: GHSA-756m-w6hw-pq9q
References
More Google Android vulnerabilities
- TI-2026-42236 Improper authorization in Google Android KEVCVSS 3.1HIGH 8.8
- TI-2025-30821 Use after free in Google Android KEVCVSS 3.1HIGH 8.8
- TI-2023-17777 Improper privilege management in Google Android KEVCVSS 3.1HIGH 8.8
- TI-2025-30872 Integer overflow in Google Android KEVCVSS 3.1HIGH 8.4
- TI-2024-21766 there is a possible way to bypass due to a logic error in the code. KEVCVSS 3.1HIGH 8.1
- TI-2025-30849 Missing authentication in Google Android KEVCVSS 3.1HIGH 7.8
Sources
- CVE-2023-20924 · CVE Program
- CVE-2023-20924 · NVD
- FIRST EPSS
- GHSA-756m-w6hw-pq9q · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences