CVE-2026-3932 json
Insufficient policy enforcement in PDF in Google Chrome on Android prior to 146.0.7680.71 allowed a remote attacker to bypass navigation re…
published 7mo ago modified 4mo ago also EUVD-2026-11456
- cvss
- 6.5
- 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 11%
- public exploits
- 0
- none known
Summary
Insufficient policy enforcement in PDF in Google Chrome on Android prior to 146.0.7680.71 allowed a remote attacker to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Medium)
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-3932
- 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
Is CVE-2026-3932 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-284 Improper Access Control
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/03/stable-channel-update-for-desktop_10.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/478296121
permissions-required
Sources
- CVE List CVE-2026-3932
- NVD CVE-2026-3932
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.