CVE-2026-15132: Uninitialized Use in V8 in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrar

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

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

Q: Is CVE-2026-15132 being exploited?

CVE-2026-15132 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-15132 affect?

CVE-2026-15132 affects chrome. Severity is high (CVSS 8.8). Uninitialized Use in V8 in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

This month

HIGH 8.8UPGRADE

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

Uninitialized Use in V8 in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.5% (top 61%)
CISA exploited list	No
Weakness	CWE-457
Published	2026-07-08
Last modified	2026-10-25

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-07-08 23:16 UTCPublished CVE record published
2026-10-25 17:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 150.0.7871.115

Fixed in: 150.0.7871.115

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 150.0.7871.115 (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-15132?

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

Is CVE-2026-15132 being exploited?

CVE-2026-15132 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-15132 affect?

CVE-2026-15132 affects chrome. Severity is high (CVSS 8.8). Uninitialized Use in V8 in Google Chrome prior to 150.0.7871.115 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

How urgent is CVE-2026-15132?

Priority 41/100. High severity

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-14121 CRITICAL 9.8 UPGRADE Use after free in Chromoting in Google Chrome on Linux prior to 150.0.7871.47 allowed a remote attacker to exe
CVE-2026-14104 CRITICAL 9.8 UPGRADE Insufficient validation of untrusted input in WebAppInstalls in Google Chrome prior to 150.0.7871.47 allowed a
CVE-2026-13776 CRITICAL 9.8 UPGRADE Type Confusion in Dawn in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised t
CVE-2026-13782 CRITICAL 10.0 UPGRADE Use after free in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromise
CVE-2026-13775 CRITICAL 9.8 UPGRADE Use after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised th

References

← Back to latest CVEs