Skip to main content

Android CVE-2026-58823

| EUVDEUVD-2026-74024 HIGH
Classic Buffer Overflow (CWE-120)
2026-09-08 security@android.com GHSA-89fm-29gh-m87g
7.8
CVSS 3.1 · Vendor: android
View

Attack ChainAIDerived

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

  1. Access
    Install low-privilege app on target Android 17 device
  2. Delivery
    Access Android NFC subsystem from app context
  3. Exploit
    Send crafted ST-proprietary NCI message to stpropnci_process_std
  4. Execution
    Trigger missing bounds check causing buffer overflow
  5. Persist
    Corrupt adjacent memory in privileged NFC process
  6. Impact
    Escalate privileges to system-level control

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

Requires a local attacker with low-privilege code execution on an Android 17 device that physically incorporates an STMicroelectronics NFC controller - devices using NXP or other NFC controllers do not include stpropnci_std.cc and are not affected. The attacker must be able to interact with the NFC subsystem from their process context, which is accessible to applications with standard app-level permissions. No user interaction is required after the malicious application is installed and invokes the vulnerable code path. Limiting factors include: local-only access (no remote exploitation path), specific ST NFC hardware dependency narrowing the vulnerable device population, and no automation of the exploit per SSVC Automatable rating of 'no.'

Impact

The CVSS 7.8 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately characterizes the risk: exploitation is limited to local attackers with at least low-privilege code execution, reducing the attack surface compared to network-exploitable vulnerabilities. The AC:L metric indicates low complexity once local access is obtained, meaning no race condition or specific timing is required. SSVC rates Automatable as 'no,' consistent with the local-only vector and device-specific hardware prerequisite. Technical Impact is 'total,' confirming full compromise of the vulnerable system upon successful exploitation. EPSS data was not provided; exploitation status is 'none' per SSVC, meaning no public proof-of-concept or active exploitation has been observed. The hardware dependency on STMicroelectronics NFC controllers meaningfully narrows the population of vulnerable devices below the full Android 17 install base. Overall real-world priority is moderate: high severity for affected devices, but practically constrained by local-only access and specific hardware requirement.

Exploit ScenarioDerived

A malicious application installed on an Android 17 device with an STMicroelectronics NFC controller executes with standard low-privilege app permissions and submits crafted ST-proprietary NCI protocol data targeting the stpropnci_process_std() function. The missing bounds check allows the crafted payload to overflow an internal buffer, corrupting adjacent memory in the NFC daemon or a privileged system process. The attacker leverages the corruption to redirect execution flow and achieve privilege escalation to a higher-privilege Android system context. No public exploit code has been identified at time of analysis.

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 17's STMicroelectronics NCI (NFC Controller Interface) driver allows a low-privileged local process to gain full system-level control via a missing bounds check in stpropnci_process_std() of stpropnci_std.cc. The missing input validation triggers a CWE-120 buffer overflow, achieving C:H/I:H/A:H impact with no user interaction required. No public exploit has been identified at time of analysis per SSVC exploitation status 'none,' though the SSVC Technical Impact is rated 'total.'

RemediationAI

Apply the Android September 2026 Security Bulletin patches (security patch level 2026-09-01 or later), available from Google and OEM device partners via the advisory at https://source.android.com/docs/security/bulletin/2026/2026-09-01. An exact patched build number is not independently extractable from the provided references but the bulletin date anchors the fix. As a compensating control pending OEM patch rollout, enterprise administrators can restrict or disable NFC functionality for untrusted or sideloaded applications via device management policy (MDM/EMM), reducing the attack surface at the cost of NFC-dependent feature availability. Limiting installation of untrusted third-party APKs provides an additional layer of defense given the local-execution prerequisite.

Affected VersionsENISA

Android 17

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

The vulnerability resides in stpropnci_std.cc, a C++ source file implementing ST (STMicroelectronics) proprietary extensions to the NCI (NFC Controller Interface) protocol within the Android NFC stack. CWE-120 (Buffer Copy without Checking Size of Input) identifies the root cause as a failure to validate input bounds before processing data in stpropnci_process_std(). The NCI protocol mediates communication between the Android host and the NFC controller hardware; the 'stprop' prefix indicates ST-proprietary command handling, meaning only devices using STMicroelectronics NFC controllers are in-scope. A malformed proprietary NCI message or locally injected input can overflow a buffer, corrupting adjacent memory structures and enabling controlled code execution at a higher privilege level. Affected product version is Android 17 per EUVD-2026-74024.

Know when the next one hits your stack

  • 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 low-privilege access triggers ST NCI buffer overflow with no user interaction, achieving full system compromise on affected hardware.

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 stpropnci_process_std of stpropnci_std.cc, there is a possible memory safety issue due to a missing bounds check. 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 17 devices with STMicroelectronics NFC drivers are vulnerable to local privilege escalation enabling full system compromise, with no patch currently available. This affects organizations with Android 17 deployments, BYOD programs, and NFC-enabled mobile infrastructure. Immediate action is required to inventory vulnerable devices and implement compensating controls pending vendor patch release.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: disabling NFC on devices where not operationally required; restricting application-level permissions for NFC access; limiting local device access and enforcing physical security controls; establishing continuous monitoring for vendor security advisories; prioritizing upgrade pathways to patched Android versions when released.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
High
Android 17 widely deployed globally, though ST NFC hardware narrows scope
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.

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