Quick answers
- Is CVE-2026-0092 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0092 being exploited in the wild.
- How severe is CVE-2026-0092?
- High severity, with a CVSS score of 7.8, published 17 June 2026.
- Which products and versions are affected?
- Google Android 17.0.
- Is there a fix for CVE-2026-0092?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-0092 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-0092?
- Check whether you run Google Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in the Android Package Manager component (specifically within the Framework) arises from a missing permission check. This flaw allows a local attacker to bypass the device lock controller, leading to local escalation of privilege (EoP). The attack requires no additional execution privileges and no user interaction. The issue is addressed in Android 17 with security patch levels of 2026-07-01 or later. While some sources list a CVSS 4.0 score of 10.0, the local nature of the escalation typically aligns with the reported high severity (CVSS 7.8).
Affected products
- Google Android 17.0
Timeline
- 2026-06-16: advisory: Android 17 Security Release Notes published
- 2026-06-17: disclosed: NVD publication date