CVE-2026-0160
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 · uneditedIn TextRtpPayloadDecoderNode::DecodeT140 of TextRtpPayloadDecoderNode.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is not 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 · high confidenceA missing bounds check in TextRtpPayloadDecoderNode::DecodeT140 in TextRtpPayloadDecoderNode.cpp allows an out-of-bounds write during RTP T.140 text payload decoding, enabling remote code execution without requiring privileges or user interaction.
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 dataall versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Android platformCheck if the device or system is running Android OS (e.g., via 'getprop ro.build.version.release' or system information)Affected if The system is running any version of Google Android OS
-
Identify WebRTC RTP usageCheck if any application on the device uses WebRTC for real-time communication, particularly for text-based communication. Inspect running processes for WebRTC libraries (libwebrtc.so or similar) or check app permissions for camera/microphone/network access typical of VoIP or real-time text appsAffected if WebRTC-based applications that handle RTP streams are installed or running on the device
-
Check for T.140 text payload handlingDetermine if any installed application processes RTP T.140 text payloads. This typically occurs in real-time text communication apps, relay services for deaf/hard-of-hearing users, or IP-based telecommunications. Inspect network traffic if possible for RTP packets containing T.140 text data (standard port 5004/5005 or custom RTP ports)Affected if Any application is actively receiving or processing RTP T.140 text payload streams
-
Verify TextRtpPayloadDecoderNode presenceIf the device supports debugging, examine loaded libraries for the presence of TextRtpPayloadDecoderNode component in WebRTC libraries. This is typically embedded in libwebrtc.so or similar WebRTC runtime libraries used by communication applicationsAffected if The WebRTC library containing TextRtpPayloadDecoderNode is loaded by any application on the device
If the device runs any version of Google Android and uses any WebRTC-based application that processes RTP T.140 text payloads, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patch to address the missing bounds validation in the T.140 payload decoder; until patch available, restrict untrusted RTP input sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0160 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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