Skip to main content

Android CVE-2026-55273

| EUVDEUVD-2026-74017 HIGH
Improper Input Validation (CWE-20)
2026-09-08 security@android.com GHSA-xg3f-rx44-cw93
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 access (app or shell)
  2. Delivery
    Craft malformed comment-line input for AnnotationProcessor
  3. Exploit
    Submit input to AppendCommentLine triggering CWE-20 validation failure
  4. Execution
    Exploit improper processing to escalate privileges
  5. Impact
    Achieve full C/I/A impact on device

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires local code execution on an affected Android device with at minimum low-privilege app-level access (consistent with PR:L in the CVSS vector). The attacker must be able to supply crafted input to the AppendCommentLine function of AnnotationProcessor.cpp - which may require either running in a build environment context or triggering the annotation processor through an app or system service. No user interaction is required once the attacker has device access. Limiting factors: AV:L constrains this to actors with physical or local software access to the device; S:U means the privilege escalation is bounded to the vulnerable system's own privilege boundary and does not directly break out to other systems. The 'supply chain risk' framing is not independently confirmed and may indicate the processor runs in build pipelines rather than runtime user space - if so, exploitation conditions may differ from a standard local app exploit.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H scores 7.8, indicating local exploitation with low complexity, low-privilege requirements, and no user interaction needed. Real-world risk is meaningful given Android's ubiquity, but the AV:L constraint limits exposure to scenarios where the attacker already has local code execution (e.g., a malicious app or an insider). No KEV listing and no public exploit code has been identified at time of analysis. The 'supply chain risk' framing is an unusual qualifier in CVE descriptions and warrants independent verification - it may elevate the effective impact beyond a single device if the annotation processor runs in CI/CD or shared build environments. EPSS data is not available in the provided intelligence. The combination of no required user interaction and low-privilege local access makes this moderately automatable once device foothold is achieved.

Exploit ScenarioDerived

An attacker installs a malicious application on an Android 16 or 17 device that crafts specially malformed comment-line input targeting the AnnotationProcessor's AppendCommentLine function. The malformed input passes validation checks and triggers privilege escalation, granting the attacker elevated system access without any user interaction beyond the initial app installation. No public exploit code has been identified at time of analysis, but the low complexity rating indicates exploitation would be straightforward once the trigger input is understood.

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 16, 16-QPR2, and 17 stems from improper input validation in the AppendCommentLine function of AnnotationProcessor.cpp. A low-privileged local attacker can exploit this CWE-20 flaw without user interaction to achieve full confidentiality, integrity, and availability impact, consistent with a complete privilege escalation on the device. Google's Android Security Bulletin for September 2026 (2026-09-01) addresses this issue; the description's explicit 'supply chain risk' framing is atypical and suggests the vulnerable code participates in a build or annotation-processing pipeline where malicious input could propagate into compiled artifacts.

RemediationAI

Apply the Android September 2026 Security Patch Level (2026-09-01) as released by Google, available through OEM firmware updates and the Android Open Source Project. Consult the official advisory at https://source.android.com/docs/security/bulletin/2026/2026-09-01 for patch confirmation and patch level verification. No exact patched build number was specified in the provided data; verify the security patch level on updated devices (Settings > About phone > Android security update). If patching is delayed for managed fleets, restrict installation of untrusted applications and enforce work profile isolation to reduce the local-attacker attack surface. No workaround short of patching is known from available sources.

Affected VersionsENISA

Android 16-qpr2
Android 16
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

AnnotationProcessor.cpp is part of Android's build or compiler toolchain - the AppendCommentLine function processes source-level annotations or comments during compilation. CWE-20 (Improper Input Validation) at this stage means the processor fails to sanitize comment content before use, enabling injection of attacker-controlled data into processed output. The 'supply chain risk' language in the description suggests the flaw could allow crafted input to affect downstream build artifacts, not merely the immediate process. Affected versions per EUVD: Android 16-QPR2, Android 16, and Android 17; no CPE string was provided but the reporter is security@android.com (Google Android Security Team), confirming Google as the vendor.

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 vector confirmed by description; PR:L reflects low-privilege app access needed; full C/I/A consistent with local privilege escalation to system/root.

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 AppendCommentLine of AnnotationProcessor.cpp, there is a possible supply chain risk due to improper input validation. 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 16, 16-QPR2, and 17 contain a local privilege escalation vulnerability in AnnotationProcessor.cpp that allows low-privileged users to fully compromise device confidentiality, integrity, and availability without user interaction. With no current patch available, organizations deploying these Android versions in corporate or BYOD environments face immediate risk to sensitive mobile device data and system integrity.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: restricting physical access to affected devices, enforcing strict local privilege controls to limit attacker capabilities, disabling annotation-processing and build-pipeline features that may trigger the vulnerability, implementing enhanced detection and alerting for privilege escalation attempts on affected devices, and maintaining offline backups to mitigate data loss from potential integrity or availability attacks.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Ubiquitous
Android is the world's most widely deployed mobile OS
Data Quality
6 sources
Confidence: High

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.

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