CVE-2026-5903 json
Policy bypass in IFrameSandbox in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who convinced a user to engage in specific…
published 7mo ago modified 3mo ago also EUVD-2026-20727
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
Policy bypass in IFrameSandbox in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who convinced a user to engage in specific UI gestures to bypass navigation restrictions via a crafted HTML page. (Chromium security severity: Low)
Patch / fix
- google chrome 147.0.7727.55
- chromium Debian 12 147.0.7727.55-1~deb12u1
- chromium Debian 13 147.0.7727.55-1~deb13u1
- chromium Debian 14 147.0.7727.55-1
debian advisories DEBIAN-CVE-2026-5903
- chromium openSUSE Leap 16.0 147.0.7727.137-bp160.1.1
- chromium openSUSE Tumbleweed 147.0.7727.55-1.1
opensuse advisories openSUSE-SU-2026:20660-1openSUSE-SU-2026:10530-1
- qt6-qtwebengine Alpine 3.23 6.10.3-r1
- qt6-qtwebengine Alpine 3.24 6.11.0-r3
alpine advisories ALPINE-CVE-2026-5903
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-5903 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-5903 updated cvss 6.1
chromium-browser: Policy bypass in IFrameSandbox
-
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
- 6mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-11).
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 |
| 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-693 Protection Mechanism Failure
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/04/stable-channel-update-for-desktop.html
release-notes, vendor-advisory
-
issues.chromium.org
/issues/483771899
issue-tracking, permissions-required
Sources
- CVE List CVE-2026-5903
- NVD CVE-2026-5903
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.