Incorrect authorization in Blink in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to bypass web origin policy via a…
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 156.0.8078.47
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 156.0.8078.47.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure?/25Exposure: unknown (data gap). No advisory context yet
- Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
- Severity7/10Rated high by Chrome
- No patch0/5No signal
What would change the score
- Would score about 82 if added to CISA KEV
- Would score about 77 if CISA's SSVC rates exploitation active
- Would score about 49 if advisories confirm default setups are exposed
CVE-2026-120930 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated high by Chrome and affects Chrome; fixed in 156.0.8078.47.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- High (Chrome)
- Fix
- Fixed in 156.0.8078.47
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Google Chrome desktop web browser is affected by this flaw in its Blink rendering engine. A remote attacker could exploit it by luring a user to a specially crafted web page, bypassing web origin security restrictions and potentially accessing data from other sites.
Read the original description
Incorrect authorization in Blink in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: High)
What to do
Upgrade to a fixed version: 156.0.8078.47.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Google Chrome
From 156.0.8078.47 · fixed in 156.0.8078.47
Evidence 2
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120930
Is CVE-2026-120930 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-120930?
Chrome: from 156.0.8078.47 before 156.0.8078.47.Source: cve.now feed data
How do I fix CVE-2026-120930?
Upgrade to a fixed version: 156.0.8078.47.Source: cve.now feed data