CVE-2026-3941 json
Insufficient policy enforcement in DevTools in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrict…
published 7mo ago modified 4mo ago also EUVD-2026-11472
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
Insufficient policy enforcement in DevTools in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
Patch / fix
- google chrome 146.0.7680.71
- chromium Debian 12 146.0.7680.71-1~deb12u1
- chromium Debian 13 146.0.7680.71-1~deb13u1
- chromium Debian 14 146.0.7680.71-1
debian advisories DEBIAN-CVE-2026-3941
- chromium openSUSE Leap 16.0 146.0.7680.177-bp160.1.1
- chromium openSUSE Tumbleweed 146.0.7680.80-1.1
opensuse advisories openSUSE-SU-2026:20460-1openSUSE-SU-2026:10376-1
- qt6-qtwebengine Alpine 3.23 6.10.1-r10
- qt6-qtwebengine Alpine 3.24 6.10.2-r8
alpine advisories ALPINE-CVE-2026-3941
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2026-3941 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-3941 updated cvss 4.3
chromium-browser: Insufficient policy enforcement in DevTools
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-602 Client-Side Enforcement of Server-Side Security
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/03/stable-channel-update-for-desktop_10.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/474670215
permissions-required
Sources
- CVE List CVE-2026-3941
- NVD CVE-2026-3941
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.