CVE-2026-7339Network attack vector

Heap corruption via unchecked WebRTC frame size

Published Apr 28, 2026 · Updated Apr 28, 2026

Heap buffer overflow in WebRTC in Google Chrome before 147.0.7727.138 allows remote attackers to corrupt heap memory via crafted HTML. The audio processor in media/webrtc/audio_processor.cc used a debug-only assertion to compare WebRTC's calculated frame size with the output buffer's frames-per-buffer, leaving release builds without this required check. Opening attacker-controlled HTML must reach WebRTC audio processing; a mismatched frame size can overrun heap storage, while public records report no exploitation in the wild.

CVSS severity8.8
High
EPSS probability0.33%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Heap buffer overflow in WebRTC in Google Chrome before 147.0.7727.138 allows remote attackers to corrupt heap memory via crafted HTML. The audio processor in media/webrtc/audio_processor.cc used a debug-only assertion to compare WebRTC's calculated frame size with the output buffer's frames-per-buffer, leaving release builds without this required check. Opening attacker-controlled HTML must reach WebRTC audio processing; a mismatched frame size can overrun heap storage, while public records report no exploitation in the wild.

The record

CVE
CVE-2026-7339
Published
Apr 28, 2026
Updated
Apr 28, 2026
Vendor
Go standard library
Product
Google Chrome
Classifications
CWE-122, T1203
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 28, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 28, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=147.0.7727.138 <147.0.7727.138

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Go standard library · Google Chromeversion=147.0.7727.138 <147.0.7727.138

Published CVSS scores

8.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-122Heap-based Buffer Overflow
T1203Exploitation for Client Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo