CVE-2026-0149: In RtpSession::rtpSendRtcpPacket, there is a possible OOB write due to a heap buffer overflow
In RtpSession::rtpSendRtcpPacket, there is a possible OOB write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
Metrics
- CVSS v3.1
- 8.8
- Severity
- HIGH
- Fixed in
- —
- Affected Products
- 1
HarborGuard Analysis
Synopsis
This is a heap buffer overflow vulnerability in the Android kernel, specifically in the RtpSession::rtpSendRtcpPacket function responsible for handling RTCP network packets. The flaw is reachable over the network by any authenticated user with a low-privilege account, and requires no action from a victim on the target device. Successful exploitation gives an attacker full remote code execution on the affected device. No fix version has been published yet; HarborGuard is tracking this advisory and will make a patched-image rebuild available the moment an upstream fix ships.
HarborGuard Coverage
Detection is available across every HarborGuard environment: the CVE is ingested from upstream feeds within minutes of publication and matched against all customer images, including custom-built images that bundle the Android kernel or derived components. Any image found to carry an affected kernel version is flagged immediately in the customer pipeline.
AvailableHarborGuard scores this CVE at 8.8 HIGH using the published CVSS v3.1 vector and can weight that score against each customer organization's compliance policy to surface it at the appropriate severity tier. Triage results are routed to the inbox configured for the relevant team within each customer environment.
AvailableNo upstream fix has been published for this CVE. HarborGuard re-checks the advisory on every ingest cycle and will make a patched-image rebuild available automatically the moment Google publishes a fix version. For customers with auto-remediation enabled, the rebuild, regression run, and PR against affected workloads will follow without manual intervention once that fix appears.
Pending upstreamExploit Conditions
- Network reachabilityRequired
The vulnerable function processes RTCP network packets, so an attacker must be able to reach the service over the network to deliver a malformed packet.
- AuthenticationRequired
The CVSS vector specifies PR:L, meaning a low-privilege account or session credential is sufficient; no administrative access is required.
- Victim interactionNot required
The CVSS vector specifies UI:N; the attacker does not need to trick or wait for any user to take an action.
- Attack complexityDetail
The CVSS vector specifies AC:L, meaning the exploit is reliable and imposes no special environmental conditions or timing requirements on the attacker.
Blast Radius
- Executes arbitrary code in the context of the Android kernel, giving the attacker full control over the compromised device.
- Reads any data accessible to the kernel, including credentials, session tokens, and application data stored on the device.
- Writes or modifies any kernel-accessible memory, allowing tampering with OS state, application data, or persisted storage.
- Crashes or destabilizes the kernel, causing a full device outage or forcing a reboot that disrupts running workloads.
How HarborGuard Handles This
Available on HarborGuard: because no upstream fix exists for CVE-2026-0149 at this time, HarborGuard continuously monitors the advisory on every ingest cycle and will trigger a patched-image rebuild automatically the moment Google publishes a fix version. For customers with auto-remediation enabled, that rebuild will be followed immediately by a regression run and a PR opened against affected workloads, with median time from fix publication to merged patch PR for high-severity issues around 90 minutes. While no patch is available, recommended compensating controls include applying network policy isolation to restrict which sources can send RTCP traffic to affected workloads, egress filtering to limit lateral movement in the event of compromise, and disabling or gating any feature that exposes RTP or RTCP handling to untrusted network peers where operationally feasible.
- Google / AndroidAndroid kernel
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H