Quick answers
- Is CVE-2026-0019 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0019 being exploited in the wild.
- How severe is CVE-2026-0019?
- High severity, with a CVSS score of 7.8, published 17 June 2026.
- Which products and versions are affected?
- Google Android 17.
- Is there a fix for CVE-2026-0019?
- 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-0019 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-0019?
- 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 logic error exists within the SettingsLib component of Android 17, classified as Improper Privilege Management (CWE-269). This vulnerability allows a local attacker with low privileges to disable system components, leading to a full escalation of privilege (EoP). The attack does not require additional execution privileges or user interaction. The issue is addressed in the Android 17 security release with a patch level of 2026-07-01 or later.
Affected products
- Google Android 17
Timeline
- 2026-06-16: advisory: Android 17 Security Release Notes published
- 2026-06-17: disclosed: NVD publication date