Skip to main content
Menu
CVEs

Google Chrome authorization bypass in CacheStorage

CVE-2026-121063Published November 3, 2026, updated

8.1HighCISA-ADP
Exploited
Proof of concept public, per CISA
Fix
Fixed in 157.0.8103.38
Who is exposed
Not reported

Summary

Incorrect authorization in CacheStorage in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)

What to do

Upgrade to a fixed version: 157.0.8103.38.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-121063 (Incorrect authorization in CacheStorage in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-121063 (entry last updated 2026-11-09):
Affected:
- Google Chrome: from 157.0.8103.38, fixed in 157.0.8103.38
Fixed versions: 157.0.8103.38.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-121063 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-121063 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html
- https://issues.chromium.org/issues/499181801
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-121063
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-121063"}.

Affected versions

cve.now Index

51of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 91 if added to CISA KEV
  • Would score about 86 if CISA's SSVC rates exploitation active
  • Would score about 66 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now6 days
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Public exploit activity

100%0Posted on X by cve.nowNov 3Nov 22
  • EPSS: 0.29%
  • Posted on X by cve.now Nov 9

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 4

Questions about CVE-2026-121063

Is CVE-2026-121063 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-121063?

Chrome: from 157.0.8103.38 before 157.0.8103.38.

Source: cve.now feed data

How do I fix CVE-2026-121063?

Upgrade to a fixed version: 157.0.8103.38.

Source: cve.now feed data

Why is it rated 8.1 High?

CVSS 8.1 scores the worst case. Chrome rates it Medium.

No corrections so far. Something wrong on this page? Report an error.