CVE-2026-28594
CVE-2026-28594 is a CWE-693 vulnerability in platform/frameworks/base. O3 Security confirms whether CVE-2026-28594 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-28594.
Real-World Exposure
platform/frameworks/base📦platform/system/core📦platform/frameworks/base📦platform/system/core📦platform/frameworks/base📦platform/system/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.
Description
In multiple locations, there is a possible use after free due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Android | platform/frameworks/base | ≥ 17-next:0&&< 17-next:2026-09-01 | 17-next:2026-09-01 |
| 📦Android | platform/system/core | ≥ 17-next:0&&< 17-next:2026-09-01 | 17-next:2026-09-01 |
| 📦Android | platform/frameworks/base | ≥ 16-qpr2:0&&< 16-qpr2:2026-09-01 | 16-qpr2:2026-09-01 |
| 📦Android | platform/system/core | ≥ 16-qpr2:0&&< 16-qpr2:2026-09-01 | 16-qpr2:2026-09-01 |
| 📦Android | platform/frameworks/base | ≥ 17:0&&< 17:2026-09-01 | 17:2026-09-01 |
| 📦Android | platform/system/core | ≥ 17:0&&< 17:2026-09-01 | 17:2026-09-01 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update platform/frameworks/base to 17-next:2026-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28594 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-28594 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-28594. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-28594 in your dependencies?
O3 detects CVE-2026-28594 across Android dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.