Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 Android
Not in CISA KEV

CVE-2026-58839

CVE-2026-58839 is a CWE-120 vulnerability in platform/system/incremental_delivery. O3 Security confirms whether CVE-2026-58839 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Also known asA-466091304
Published
Sep 1, 2026
Updated
Sep 8, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Sep 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-58839.

Real-World Exposure

5 pkgs affected
📦platform/system/incremental_delivery📦platform/system/incremental_delivery📦platform/system/incremental_delivery📦platform/system/incremental_delivery📦platform/system/incremental_delivery

Real-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 forEachLine of MountRegistry.cpp, there is a possible out of bounds read due to a buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦Androidplatform/system/incremental_delivery17-next:0&&< 17-next:2026-09-0117-next:2026-09-01
📦Androidplatform/system/incremental_delivery15:0&&< 15:2026-09-0115:2026-09-01
📦Androidplatform/system/incremental_delivery16:0&&< 16:2026-09-0116:2026-09-01
📦Androidplatform/system/incremental_delivery16-qpr2:0&&< 16-qpr2:2026-09-0116-qpr2:2026-09-01
📦Androidplatform/system/incremental_delivery14:0&&< 14:2026-09-0114:2026-09-01

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/system/incremental_delivery. 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.

  2. Fix

    Update platform/system/incremental_delivery to 17-next:2026-09-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-58839 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-58839 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-58839. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In forEachLine of MountRegistry.cpp, there is a possible out of bounds read due to a buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
O3 Security · Impact-Aware SCA

Is CVE-2026-58839 in your dependencies?

O3 detects CVE-2026-58839 across Android dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2026-58839: platform/system/increment…… | O3 Security