Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-privileged local foothold
-
DeliveryDeliver crafted RTP packet via media path
-
ExploitTrigger integer overflow in RtpPacket::decodePacket
-
ExecutionCause out-of-bounds memory access
-
ImpactEscalate 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
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
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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.
Primary rating from Vendor (Google_Devices).
CVSS VectorVendor: Google_Devices
Lifecycle Timeline
3DescriptionCVE.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
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.
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
EUVD-2026-37214
GHSA-85m7-m94v-5pch
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB