CVE-2026-95327: Information leak in Networking in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to leak sensi

Q: How do I fix CVE-2026-95327?

chrome: upgrade to 154.0.8037.57. Exact commands for each OS are on this page.

Q: Is CVE-2026-95327 being exploited?

CVE-2026-95327 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-95327 affect?

CVE-2026-95327 affects chrome. Severity is medium (CVSS 6.5). Information leak in Networking in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to leak sensitive information via a crafted HTML page. (Chromium security severity: Low)

Q: How urgent is CVE-2026-95327?

Priority 27/100. No elevated risk signals yet.

Routine

MEDIUM 6.5UPGRADE

CVE-2026-95327 is a medium-severity flaw (CVSS 6.5) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Information leak in Networking in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to leak sensitive information via a crafted HTML page. (Chromium security severity: Low)

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 84%)
CISA exploited list	No
Weakness	CWE-200
Published	2026-09-29
Last modified	2026-10-01

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-01 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-29 18:17 UTCPublished CVE record published
2026-10-01 04:18 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 154.0.8037.57

Fixed in: 154.0.8037.57

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. UPGRADE to 154.0.8037.57 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chrome

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chrome

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-95327?

chrome: upgrade to 154.0.8037.57. Exact commands for each OS are on this page.

Is CVE-2026-95327 being exploited?

CVE-2026-95327 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-95327 affect?

CVE-2026-95327 affects chrome. Severity is medium (CVSS 6.5). Information leak in Networking in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to leak sensitive information via a crafted HTML page. (Chromium security severity: Low)

How urgent is CVE-2026-95327?

Priority 27/100. No elevated risk signals yet.

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-7898 HIGH 8.8 UPGRADE Use after free in Chromoting in Google Chrome on Linux prior to 148.0.7778.96 allowed a remote attacker to exe
CVE-2026-7951 HIGH 8.8 UPGRADE Out of bounds write in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arb
CVE-2026-7992 HIGH 8.8 UPGRADE Insufficient validation of untrusted input in UI in Google Chrome on Linux, ChromeOS prior to 148.0.7778.96 al
CVE-2026-7902 HIGH 8.8 UPGRADE Out of bounds memory access in V8 in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute
CVE-2026-7928 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome on Windows prior to 148.0.7778.96 allowed a remote attacker to execu

References

← Back to latest CVEs