Skip to main content

Android CVE-2026-58839

| EUVDEUVD-2026-74025 HIGH
Classic Buffer Overflow (CWE-120)
2026-09-08 security@android.com GHSA-c7m8-f924-9rgf
7.8
CVSS 3.1 · Vendor: android
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain low-privilege local execution on device
  2. Delivery
    Trigger forEachLine buffer overflow in MountRegistry.cpp
  3. Exploit
    Out-of-bounds read corrupts adjacent memory
  4. Execution
    Hijack execution flow in privileged storage subsystem
  5. Persist
    Escalate to elevated system privileges
  6. Impact
    Full device compromise (C:H/I:H/A:H)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer copy size validation
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires local code execution on the target Android device with at minimum a low-privileged application context (PR:L). The attacker must be able to trigger the storage volume management subsystem's forEachLine parsing routine, which occurs during normal mount registry operations. No user interaction is required once the attacker's code is executing on the device. Exploitation is bounded by the requirement for prior local code execution - remote unauthenticated exploitation is not possible given AV:L. Devices running Android 14, 15, 16, or 16-qpr2 that have not applied the September 2026 security patch are vulnerable. SSVC notes the attack is not automatable, suggesting reliable exploitation requires targeted effort rather than trivial scripted abuse.

Impact

The CVSS 7.8 base score (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects a local, low-complexity privilege escalation with total system impact. SSVC corroborates the severity with a 'total' technical impact rating, though it also notes exploitation status as 'none' and automatable as 'no', meaning opportunistic mass exploitation is unlikely. EPSS data is absent from the provided intelligence; however, the combination of a locally exploitable memory corruption primitive, no user interaction requirement, and total impact across four Android versions represents a meaningful real-world risk - particularly for rooted-device threats, malicious applications that have obtained low-privilege execution, or post-initial-access scenarios. The absence of KEV listing and no public POC at time of analysis moderates urgency relative to the raw CVSS score. The local attack vector limits the threat primarily to on-device exploitation rather than remote network-based attacks.

Exploit ScenarioDerived

An attacker installs a malicious application granted only standard low-privilege permissions, or exploits a separately compromised app process already running on the device. The malicious code triggers the forEachLine buffer overflow in MountRegistry.cpp by inducing the storage subsystem to process crafted or oversized line data, corrupting adjacent memory. This memory corruption is then leveraged to redirect execution flow and escalate privileges to a higher system process level, granting full read/write/execute control over the device.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 08, 2026

Local privilege escalation in Android's MountRegistry component across Android 14, 15, 16, and 16-qpr2 allows a low-privileged process to achieve full device compromise via a buffer overflow in the forEachLine function of MountRegistry.cpp. The flaw triggers an out-of-bounds read that can corrupt adjacent memory, enabling an attacker to elevate from a sandboxed app or low-privilege process to a higher system privilege level without any user interaction. No public exploit has been identified at time of analysis, though SSVC rates the technical impact as total.

RemediationAI

Apply the Android September 2026 security patch level (2026-09-01) as published in the Android Security Bulletin at https://source.android.com/docs/security/bulletin/2026/2026-09-01. Device manufacturers (OEMs) must integrate this patch into their own update distributions; users should install the latest available security update from their device vendor. For enterprise environments managing Android fleets via MDM, enforce minimum security patch level 2026-09-01 through policy and flag non-compliant devices. No exact patched build version was independently specified in the provided data beyond the bulletin reference. If patching is delayed, restrict sideloading and installation of untrusted applications to reduce the surface available for a low-privilege attacker to reach the vulnerable code path - though this is a compensating control, not a fix.

Affected VersionsENISA

Android 15
Android 16
Android 16-qpr2
Android 14

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MountRegistry.cpp is part of Android's storage volume management subsystem, likely associated with the vold (volume daemon) or a related system service responsible for parsing and managing mount point records. The forEachLine function iterates over line-by-line data - likely sourced from procfs mount tables or similar structured text - and performs a buffer copy (CWE-120: Classic Buffer Copy without Checking Size of Input) without adequately bounding the read length. Because this component operates at a privileged system level above normal app sandboxes, a successful exploitation directly bridges the gap from a low-privilege execution context to a significantly elevated one. Affected versions span Android 14, 15, 16, and 16-qpr2, indicating the vulnerable code path existed across multiple major Android releases before the September 2026 security bulletin.

Know when Android gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (android) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local-only attack requiring low-privilege execution; no user interaction; full C/I/A impact on the vulnerable system process, no scope change.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (android).

CVSS VectorVendor: android

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Android's MountRegistry component contains a local privilege escalation vulnerability (CVE-2026-58839) affecting Android 14, 15, and 16 devices, allowing any application on a device to achieve complete system compromise without user interaction. Organizations using Android devices in enterprise or BYOD programs face critical risk, as attackers could exploit seemingly benign apps to gain full device control and access to all sensitive data. No vendor patch is currently available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Implement application-allowlisting through MDM to restrict installation to pre-approved vendors only, enforce strict app permission controls (especially system-level access), disable sideloading and developer mode on enterprise devices, and enable system-level monitoring for privilege-escalation attempts. This vulnerability requires local access via a running application; remote exploitation is not possible.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Ubiquitous
Android is deployed on billions of active consumer and enterprise devices globally.
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

CVE-2015-3105 CRITICAL POC
10.0 Jun 10

Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows and OS X and before 11.2.202.466

CVE-2015-3864 CRITICAL POC
10.0 Oct 01

Integer underflow in the MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in mediaserver in A

CVE-2013-4710 CRITICAL POC
9.3 Mar 03

Android 3.0 through 4.1.x on Disney Mobile, eAccess, KDDI, NTT DOCOMO, SoftBank, and other devices does not properly imp

CVE-2015-1538 CRITICAL POC
10.0 Oct 01

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android bef

CVE-2024-21633 HIGH POC
7.8 Jan 03

Apktool versions 2.9.1 and prior contain a path traversal vulnerability when processing Android APK files. Malicious APK

CVE-2017-13156 HIGH POC
7.8 Dec 06

An elevation of privilege vulnerability in the Android system (art). Rated high severity (CVSS 7.8), this vulnerability

CVE-2016-2107 MEDIUM POC
5.9 May 05

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a

CVE-2015-3106 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2015-3107 CRITICAL POC
10.0 Jun 10

Use-after-free vulnerability in Adobe Flash Player before 13.0.0.292 and 14.x through 18.x before 18.0.0.160 on Windows

CVE-2013-4787 CRITICAL POC
9.3 Jul 09

Android 1.6 Donut through 4.2 Jelly Bean does not properly check cryptographic signatures for applications, which allows

CVE-2014-7911 HIGH
7.2 Dec 15

luni/src/main/java/java/io/ObjectInputStream.java in the java.io.ObjectInputStream implementation in Android before 5.0.

CVE-2016-0801 CRITICAL POC
9.8 Feb 07

The Broadcom Wi-Fi driver in the kernel in Android 4.x before 4.4.4, 5.x before 5.1.1 LMY49G, and 6.x before 2016-02-01

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy