CVE-2026-0148
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 multiple functions of VideoRtpPayloadDecoderNode.cpp, there is a possible out of bounds write due to an integer overflow. 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 vulnerability in VideoRtpPayloadDecoderNode.cpp allows an integer overflow to cause an out-of-bounds write during RTP payload decoding. This can be exploited remotely to achieve code execution without any user interaction or elevated privileges, indicating the vulnerability is directly reachable via network-processed RTP streams.
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 platform is in useCheck the device or system information to verify the operating system is Google Android. On Android, you can check via Settings > About Phone > Android version, or run 'getprop ro.build.version.release' in ADB shell.Affected if The system is running any version of Google Android, which falls under the affected product range.
-
Identify RTP processing componentsSearch for processes or services that handle RTP (Real-time Transport Protocol) streams. Look for processes named or containing references to 'RTP', 'mediacodec', 'videocodec', or similar media handling components. Use 'ps -A | grep -i rtp' or check /proc/[pid]/cmdline on Android.Affected if RTP-handling components are present on the Android system, indicating the vulnerable code path could be reachable.
-
Check for applications using RTPReview installed applications that process video/audio streams, such as video conferencing apps, VoIP clients, or streaming applications. These apps may invoke the vulnerable VideoRtpPayloadDecoderNode code.Affected if Applications capable of receiving or processing RTP streams are installed and have permission to access media/Network.
-
Verify network exposure of RTP servicesCheck if any application or service is listening on RTP/RTCP ports (typically UDP ports in the range 5000-6000, or custom ports). Use 'netstat -uan' or similar network analysis tools on Android.Affected if RTP services are bound to network interfaces and reachable, making the vulnerability directly exploitable remotely.
If the Android device has any RTP-processing applications or services that can receive network RTP streams, the environment is directly affected and exploitable without user interaction.
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 bounds checking and integer overflow protection in all size/offset calculations within the RTP payload decoder functions. If a patch is available from the vendor, deploy it immediately.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0148 — 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-0148 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