Skip to main content

Google Android CVE-2026-0131

| EUVDEUVD-2026-37214 HIGH
Integer Overflow or Wraparound (CWE-190)
2026-06-16 Google_Devices GHSA-85m7-m94v-5pch
7.3
CVSS 3.1 · Vendor: Google_Devices
View

Attack ChainAIDerived

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

  1. Access
    Gain low-privileged local foothold
  2. Delivery
    Deliver crafted RTP packet via media path
  3. Exploit
    Trigger integer overflow in RtpPacket::decodePacket
  4. Execution
    Cause out-of-bounds memory access
  5. Impact
    Escalate privileges on device

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
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 access with low existing privileges (PR:L) plus user interaction (UI:R) - the attacker must already be able to run code or act locally (e.g., a malicious or compromised app) and the victim must perform an action that reaches the vulnerable RTP decode path (RtpPacket::decodePacket). The specific triggering configuration or RTP source is not detailed in the available sources beyond the need to pass attacker-influenced data into decodePacket. Limiting factors: no remote network vector (AV:L), the mandatory user-interaction step, and the pre-requisite of an existing low-privilege local context all narrow realistic exploitation; there is no indication of automatable or unauthenticated exploitation.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H, base 7.3 HIGH) describes a locally-exploitable integer-overflow leading to out-of-bounds access in RtpPacket::decodePacket, requiring already-present low privileges plus user interaction, with total confidentiality/integrity/availability impact on the local component. The supporting signals point to low real-world urgency: EPSS is 0.07% (0th percentile), and the SSVC decision is Exploitation=none, Automatable=no, Technical Impact=total - meaning high impact if triggered but no observed exploitation and no mass-automation path (consistent with a local-only, UI-gated vector). This is not in CISA KEV and no exploit reference is present, so it reads as a high-impact-but-low-likelihood local privilege-escalation issue rather than an actively exploited emergency. The vuln.today 'this_week' label reflects routine Android-bulletin patch cadence, not active-exploitation pressure; the AV:L vector plus required user interaction materially limit practical risk. Note a minor data gap: the NVD CPE lists the Android application platform (cpe:2.3:a:google:android) while the EUVD 'affected versions' string says 'Android kernel' and the reference is the Pixel bulletin - verify the exact affected component/versions with the Android/Pixel security bulletin.

Exploit ScenarioDerived

A low-privileged local app or logged-in user supplies a crafted RTP packet (e.g., via a media/telephony path) that triggers the integer overflow in RtpPacket::decodePacket, causing an out-of-bounds access that the attacker leverages to escalate privileges on the device. Because the CVSS vector requires user interaction (UI:R), the victim must perform some action (such as opening or accepting media content) for exploitation to succeed. No public exploit 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 – Oct 26, 2026

Integer overflow in Android's RTP packet handling routine RtpPacket::decodePacket can cause an out-of-bounds access that permits a local attacker with low privileges to escalate privileges when the user performs the required interaction. The issue is tracked against Google Android (CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:*) and has a CVSS 3.1 base score of 7.3 (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H). No public exploit has been identified at time of analysis, EPSS is 0.07% (percentile 0%), and CISA SSVC records exploitation as none.

RemediationAI

Patch available per vendor advisory: apply the Android/Pixel security update referenced in the June 2026 bulletin at https://source.android.com/docs/security/bulletin/pixel/2026/2026-06-01. The supplied data does not provide an exact fixed build or version number, so verify the applicable patch level in that bulletin before rollout. No specific workarounds are detailed in the available sources; because the CVSS vector requires local low privileges and user interaction, reducing exposure to untrusted local applications may lower the attack surface but is not a substitute for the vendor update.

Affected VersionsENISA

Android Android kernel

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 is an integer overflow (CWE-190) in RtpPacket::decodePacket, the Android routine that decodes RTP packet data. An overflow in the size or offset arithmetic can lead to an out-of-bounds access when attacker-influenced RTP data is processed. The supplied CPE cpe:2.3:a:google:android:*:*:*:*:*:*:*:* describes the Android platform broadly, while EUVD lists 'Android Android kernel' as the affected component. The CVSS vector AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H means exploitation is local, requires low existing privileges, and requires user interaction; the exact triggering configuration and RTP source are not described in the available sources.

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 (Google_Devices) PRIMARY 7.3 HIGH
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.3 HIGH

Local EoP from a crafted RTP packet requires existing low privileges (PR:L) and user interaction (UI:R); integer overflow enabling OOB access yields total local C/I/A impact.

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

Primary rating from Vendor (Google_Devices).

CVSS VectorVendor: Google_Devices

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

Lifecycle Timeline

3
CVSS changed
Oct 25, 2026 - 23:23 NVD
7.3 (None) 7.3 (HIGH)
CVE Published
Jun 16, 2026 - 18:51 cve.org
UNKNOWN (no severity yet)
CVE Published
Jun 16, 2026 - 18:51 cve.org
HIGH 7.3

DescriptionCVE.org

In RtpPacket::decodePacket, there is a possible out of bounds access due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

Executive ViewAI

Why It Matters

A high-severity integer overflow in Google Android's RTP packet handling (CVE-2026-0131) could let a local attacker with low privileges escalate privileges and gain high confidentiality and integrity impact when a user performs a required interaction. Although no public exploit has been identified, the potential for privilege escalation on widely deployed Android devices means security leadership should ensure timely remediation and interim controls to protect sensitive data and maintain compliance.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include enforcing Google Play Protect, restricting app installations from untrusted sources via MDM, monitoring for anomalous RTP traffic or privilege escalation behavior, and ensuring devices are not rooted.

Threat Intelligence Overview

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Ubiquitous
Android is among the most widely deployed OS platforms 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

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
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.

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

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