Quick answers
- Is CVE-2026-0055 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0055 being exploited in the wild.
- How severe is CVE-2026-0055?
- Informational severity, with a CVSS score of 0, published 1 June 2026.
- Which products and versions are affected?
- Google Android Framework 14, 15, 16, 16-qpr2.
- Is there a fix for CVE-2026-0055?
- A patch was published on 2026-06-05: Security patch level 2026-06-05 or later addresses this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-0055 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-0055?
- Check whether you run Google Android Framework 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 path traversal vulnerability exists in the 'createSessionInternal' method of 'PackageInstallerService.java' within the Android Framework. The flaw allows an attacker to specify an invalid directory when updating a Device Policy Controller (DPC). This is a local escalation of privilege (EoP) vulnerability that requires no additional execution privileges or user interaction. The issue affects Android versions 14, 15, 16, and 16-qpr2. Google addressed this in the June 2026 Android Security Bulletin with security patch levels of 2026-06-05 or later.
Affected products
- Google Android Framework 14, 15, 16, 16-qpr2
Timeline
- 2026-06-01: disclosed: Vulnerability published in Android Security Bulletin and NVD
- 2026-06-05: patched: Security patch level 2026-06-05 or later addresses this issue