dbcve.org
AndroidOperating system · Google

CVE-2026-0128

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In RtcpFbPacket::decodeRtcpFbPacket, there is a possible out of bounds read due to an integer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An integer overflow in RtcpFbPacket::decodeRtcpFbPacket causes an out-of-bounds read vulnerability. The function processes RTCP Feedback packets without properly validating size calculations, allowing an attacker to read adjacent memory contents through crafted packets, leading to information disclosure.

MitigationApply proper integer overflow checks and bounds validation in the decode function before processing packet length fields. Ensure all size calculations use safe integer arithmetic and validate against actual buffer limits before memory access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AndroidOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if RTCP feedback packet processing is enabled
    Check if the device runs any WebRTC, VoIP, or real-time communication services that process RTCP packets (such as video calling apps, WebRTC-based browsers, or telephony components)
    Affected if RTCP Feedback packet handling is active on the device - this is the module where the vulnerability exists
  2. Determine the WebRTC or media library in use
    Examine installed applications or system libraries for components that handle RTP/RTCP protocols (commonly found in libwebrtc, mediaserver, or com.google.android.apps.tachyon variants)
    Affected if Any WebRTC or media library that includes RtcpFbPacket::decodeRtcpFbPacket is present and processing network traffic
  3. Verify network exposure to untrusted RTCP sources
    Check whether the device accepts incoming RTP/RTCP connections from untrusted network sources, or check firewall/permission settings for apps using real-time communication
    Affected if The device can receive crafted RTCP Feedback packets from network attackers - this is the attack vector for the out-of-bounds read
  4. Confirm Android version as baseline
    Run 'adb shell getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The device runs any version of Android - per the advisory, all versions are affected by this vulnerability in the RTCP processing code

If the device processes RTCP Feedback packets through any WebRTC or media component, it is affected because the integer overflow in decodeRtcpFbPacket allows out-of-bounds memory reads via crafted packets regardless of Android version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply proper integer overflow checks and bounds validation in the decode function before processing packet length fields. Ensure all size calculations use safe integer arithmetic and validate against actual buffer limits before memory access.

Recommended fix Moderate confidence

Latest Android security patch level that includes the CVE-2026-0128 fix (check source.android.com/security bulletin for the specific release date)

  1. Check your Android device's current Android version and security patch level in Settings > About Phone > Android version
  2. Check if your device manufacturer has released a security update that includes the fix for this vulnerability (CVE-2026-0128)
  3. If an update is available, back up important data on your device
  4. Install the latest available security update or Android version for your device
  5. After updating, verify the security patch level reflects the month containing the fix (typically available within 60 days of the security bulletin publication)
Caveat Updating Android may reset some settings or remove incompatible apps; ensure backup before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0128 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0128 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data