Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Heap buffer overflow in WebRTC in Google Chrome

IdentifiersCVE-2026-9119CWE-122· Heap-based Buffer Overflow

CVE-2026-9119 is a high-severity heap buffer overflow in the WebRTC component of Google Chrome. It affects Google Chrome versions prior to 148.0.7778.179. According to the provided content, a remote attacker can trigger the flaw by getting a target to load a crafted HTML page, leading to memory corruption in WebRTC and enabling arbitrary code execution within the Chrome sandbox.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to execute arbitrary code inside the browser sandbox. The provided CVSS v3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates high potential impact to confidentiality, integrity, and availability of the sandboxed browser context.

Mitigation

If you can’t patch tonight, do this now.

Apply the vendor patch as soon as possible and ensure browsers are restarted so the update takes effect. Until patching is complete, reduce exposure by limiting access to untrusted or attacker-controlled web content, as exploitation requires a user to load a crafted HTML page. No specific workaround beyond updating is provided in the supplied content.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 148.0.7778.179 or later. The provided content indicates that Chrome Stable 148.0.7778.178/179 for Windows and Mac and 148.0.7778.178 for Linux contained the relevant security fixes; the vulnerability description specifically states affected versions are prior to 148.0.7778.179.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.