# CVE-2026-0019: Google Android SettingsLib privilege escalation via system component disabling

Source: https://junglewise.ai/threats/cve-2026-0019-google-android-settingslib-privilege-escalation-via-system  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-17. Updated: 2026-06-17  
License: CC BY 4.0 with a link back

CVE-2026-0019 · Severity: high · CVSS 7.8 · Published 2026-06-17

A logic error in the Android SettingsLib component allows for the unauthorized disabling of critical system components. This could enable a local attacker to gain elevated system privileges without any user interaction. Such an exploit could compromise device security, lead to data access, or disrupt normal operations.

Technologies: [Google Android](https://junglewise.ai/threats/technologies/android). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://source.android.com/docs/security/bulletin/android-17](https://source.android.com/docs/security/bulletin/android-17)

## Related threats

- [Google Android Bluetooth buffer overflow in acquireMemory](https://junglewise.ai/threats/cve-2026-95405-in-acquirememory-of-bt-bqr-offload-cc-there-is-a-possible-way-to)
- [ST NFC HAL out-of-bounds write in global memory](https://junglewise.ai/threats/cve-2026-95400-in-stnfc-hal-write-of-hal-st21nfc-cc-there-is-a-possible-way-to)
- [Android HEVC decoder buffer overflow in sub_layer_hrd_parameters](https://junglewise.ai/threats/cve-2026-95397-in-sub-layer-hrd-parameters-of-hevc-decoder-there-is-a-possible)
- [Android framework memory exhaustion in message queue handling](https://junglewise.ai/threats/cve-2026-59632-in-respondreceivedmessage-of-mtsmessagecontroller-cpp-there-is-a)
- [Android use-after-free in UssiController connection listener](https://junglewise.ai/threats/cve-2026-59626-in-sendinfo-of-ussicontroller-cpp-there-is-a-possible-way-to)