# CVE-2026-95376: Security feature bypass in Chrome

> An adjacent attacker can bypass system access restrictions in Google Chrome DevTools via crafted network traffic and social engineering.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-95376, ECHO-60e6-3169-a982, GHSA-9386-qgfg-gg42, MINI-cxvq-5fp6-jg7p

## What is CVE-2026-95376?

CVE-2026-95376 is a high-severity vulnerability in Google Chrome, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Externally controlled reference in DevTools in Google Chrome prior to 154.0.8037.57 allowed an adjacent attacker leveraging social engineering to bypass system access restrictions via crafted network traffic. (Chromium security severity: Medium)

Weakness: CWE-610 (Externally Controlled Reference to a Resource in Another Sphere)

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

It affects 1 product.


Products: Google Chrome.

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

Upgrade to a fixed version.

## Is CVE-2026-95376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95376 exists.

## Other vulnerabilities in Google Chrome

- [CVE-2022-4135](https://insights.sbomify.com/CVE-2022-4135/): Google Chromium GPU Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2020-16017](https://insights.sbomify.com/CVE-2020-16017/): Google Chrome Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2020-16010](https://insights.sbomify.com/CVE-2020-16010/): Google Chrome for Android UI Heap Buffer Overflow (critical 9.6, exploited in the wild)
- [CVE-2026-87491](https://insights.sbomify.com/CVE-2026-87491/): Google Chromium V8 Out of Bounds Write (high 8.8, exploited in the wild)
- [CVE-2026-85046](https://insights.sbomify.com/CVE-2026-85046/): Google Chromium V8 Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95376 and fix it if it is affected.

What it is: CVE-2026-95376 is a high-severity vulnerability in Google Chrome, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95376 exists.

Affected product: Google Chrome. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95376/ (Markdown: https://insights.sbomify.com/CVE-2026-95376/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95376
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95376
- OSV: https://osv.dev/vulnerability/CVE-2026-95376

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95376/
Summaries are generated and may contain mistakes; the official description above is the record.