Skip to main content
VulnerabilityPublished Updated

CVE-2026-3934: Google Chrome · Insufficient Policy Enforcement

Affects Google ChromeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 146.0.7680.71 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 146.0.7680.71
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Google Chrome to 146.0.7680.71.

Affected software

ProductAffectedFixed in
GoogleChromeAffected
  • >=146.0.7680.71 <146.0.7680.71
Fixed in
  • 146.0.7680.71

AI-suggested

To mitigate CVE-2026-3934, organizations and users should promptly update Google Chrome to version 146.0.7680.71 or later, where the vulnerability has been addressed. If you cannot patch yet, restrict the use of ChromeDriver to trusted environments and avoid loading untrusted or unknown HTML content during automated testing. Implement strict content security policies (CSP) and sandboxing measures to limit the impact of potential SOP bypasses. Monitor automation logs and network traffic for unusual activity that may indicate exploitation attempts. Additionally, review and harden access controls around automation infrastructure to prevent unauthorized use of ChromeDriver instances. Security teams should educate developers and testers about the risks of loading untrusted content in automation contexts and enforce best practices for secure browser automation.

Description

Insufficient policy enforcement in ChromeDriver in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)

References

Community reviews

Loading reviews…