CVE-2026-9959: Race in WebRTC in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to leak cross-...
Race in WebRTC in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
This Chrome for Windows flaw could let a malicious webpage leak limited cross-origin data through a WebRTC race condition. A user must visit a crafted page, and the attack complexity is high. Google addressed affected Chrome versions before 148.0.7778.216. No source in the bundle shows active exploitation.
Executive priority
Treat this as a timely browser patching item, not an emergency breach indicator. The business risk is limited data exposure from user browsing, reduced by high attack complexity and no active exploitation evidence in the supplied sources.
Technical view
CVE-2026-9959 is a CWE-362 race condition in WebRTC affecting Google Chrome on Windows before 148.0.7778.216. The CVSS vector is network-accessible, high complexity, no privileges, user interaction required, unchanged scope, and low confidentiality impact only. Chromium rates the issue High, while the CVSS score is 3.1.
Likely exposure
Exposure is likely on Windows endpoints running Google Chrome earlier than 148.0.7778.216. The bundle does not support claims about other operating systems, Chromium-derived browsers, or server-side products.
Exploitation context
The described attack uses a crafted HTML page and requires user interaction. The issue is not listed in KEV, and the provided sources do not report exploitation in the wild or public exploit availability.
Researcher notes
Evidence is limited to the CVE description, Chromium release reference, and issue tracker URL. Do not infer exploitability beyond a crafted HTML page. Validate exposure by version and platform, and track whether Google later expands affected scope or publishes technical detail.
Mitigation direction
Update Google Chrome on Windows to 148.0.7778.216 or later.
Verify enterprise Chrome auto-update policies are working across managed Windows endpoints.
Prioritize users with access to sensitive browser-based applications and data.
Monitor Google Chrome release notes for any amended guidance.
Validation and detection
Inventory Windows devices and record installed Chrome versions.
Confirm no managed Windows endpoint remains below 148.0.7778.216.
Review browser management telemetry for failed or deferred updates.
Check vendor sources for any newly published exploit or mitigation details.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-362: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.