CVE-2026-0162
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 ParsePayloads of AudioSdpParser.cpp, there is a possible memory corruption due to type confusion. 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 · moderate confidenceA type confusion vulnerability in the ParsePayloads function of AudioSdpParser.cpp allows memory corruption during SDP audio payload parsing. This enables remote code execution without user interaction or additional privileges, as the parser improperly handles object types leading to out-of-bounds 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 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 OS is runningCheck the device OS version via 'getprop ro.build.version.release' or Settings > About Phone > Android versionAffected if The device runs any version of Google Android, as all versions are affected by this CVE
-
Identify SDP parsing component presenceCheck for presence of AudioSdpParser.cpp or related SDP audio parsing libraries in the system - look for files containing 'AudioSdpParser' or 'ParsePayloads' in /system/lib or /vendor/lib directoriesAffected if The AudioSdpParser component with vulnerable ParsePayloads function exists on the device
-
Determine SDP input exposure vectorInspect if any applications or services process SDP (Session Description Protocol) data from network sources - check for apps using WebRTC, VoIP, or SIP that accept SDP inputAffected if Applications or services that accept SDP data from untrusted sources are installed and active, enabling the attack surface
-
Check for network accessibility of media servicesReview network-bound services or APIs that handle SDP parsing - check listening ports or exposed AIDL/IPC interfaces related to media or WebRTCAffected if SDP parsing functionality is network-accessible, allowing remote exploitation without user interaction
-
Verify WebRTC or VoIP stack presenceCheck for WebRTC libraries or VoIP components in the system via 'pm list packages' or file system inspection for webrtc, sip, or voip related packagesAffected if WebRTC or SIP/VoIP stacks that utilize the vulnerable SDP parser are present on the device
If the device runs any version of Google Android and has SDP parsing capabilities (via WebRTC, VoIP, or SIP applications) exposed to network input, the environment is affected by CVE-2026-0162.
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 patches for the affected component; until then, restrict network exposure of the SDP parsing functionality and validate SDP input before passing to the parser.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0162 — 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-0162 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