Description
In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
Published: 2026-06-16
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability is a missing bounds check in the RtcpHeader::decodeRtcpHeader function of the Android RTCP stack. This omission allows a crafted RTCP packet to read memory beyond the intended bounds, potentially leaking sensitive data stored in nearby memory. The flaw results in remote information disclosure without requiring elevated privileges or additional execution rights. The weakness relates to malformed input handling, specifically a buffer overread identified by CWE-120 and CWE-125.

Affected Systems

The affected product is Google Android on Pixel devices. The vulnerability is present in the Android Runtime components that handle RTCP (Real‑time Transport Control Protocol) packets. The specific versions affected are not detailed in the information provided, so any Android build using the current RTCP header decoding code is potentially vulnerable.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity, and the EPSS score of less than 1% suggests low likelihood of exploitation at this time. The vulnerability is not listed in CISA’s KEV catalog. The attack vector is remote, network‑based, leveraging malicious RTCP packets. Successful exploitation requires only the ability to send crafted RTCP traffic to the device and does not depend on user interaction. The impact is the disclosure of confidential memory contents to the attacker, which could aid in further attacks or compromise confidentiality.

Generated by OpenCVE AI on June 17, 2026 at 21:13 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the device to the latest Android release that contains the fixed RTCP header decoder.
  • If the device cannot be updated immediately, monitor and restrict RTCP traffic from untrusted networks to reduce exposure.
  • Consider disabling or limiting RTCP functionality through system or network configuration if such an option is available.

Generated by OpenCVE AI on June 17, 2026 at 21:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 16 Jun 2026 21:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-120
CWE-125
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 16 Jun 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Google
Google android
Vendors & Products Google
Google android

Tue, 16 Jun 2026 19:30:00 +0000

Type Values Removed Values Added
Description In RtcpHeader::decodeRtcpHeader, there is a possible OOB read due to a missing bounds check. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Google_Devices

Published:

Updated: 2026-06-16T20:30:32.471Z

Reserved: 2025-10-23T08:44:53.142Z

Link: CVE-2026-0157

cve-icon Vulnrichment

Updated: 2026-06-16T19:49:01.082Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-06-16T20:16:26.327

Modified: 2026-06-16T20:42:25.013

Link: CVE-2026-0157

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-16T20:45:02Z

Weaknesses
  • CWE-120

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

  • CWE-125

    Out-of-bounds Read