CVE-2026-0162
published 2026-06-16CVE-2026-0162: In ParsePayloads of AudioSdpParser.cpp, there is a possible memory corruption due to type confusion. This could lead to remote code execution with no…
PriorityP333
EPSS
0.23%
13.9th percentile
In 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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Google Android AudioSdpParser.cpp ParsePayloads type confusion
vuldb·2026-06-16
CVE-2026-0162 Google Android AudioSdpParser.cpp ParsePayloads type confusion
A vulnerability marked as critical has been reported in Google Android. This affects the function ParsePayloads of the file AudioSdpParser.cpp. The manipulation leads to type confusion.
This vulnerability is uniquely identified as CVE-2026-0162. The attack is possible to be carried out remotely. No exploit exists.
GHSA
In ParsePayloads of AudioSdpParser.cpp, there is a possible memory corruption due to type confusion.
ghsa_unreviewed·2026-06-16
CVE-2026-0162 [HIGH] CWE-843 In ParsePayloads of AudioSdpParser.cpp, there is a possible memory corruption due to type confusion.
In 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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-06-16
Published