CVE-2026-15767: Heap buffer overflow in libyuv in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker t

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

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

Q: Is CVE-2026-15767 being exploited?

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

CVE-2026-15767 affects chrome. Severity is high (CVSS 8.8). Heap buffer overflow in libyuv in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted video file. (Chromium security severity: High)

This month

HIGH 8.8UPGRADE

CVE-2026-15767 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.

Heap buffer overflow in libyuv in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted video file. (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.4% (top 64%)
CISA exploited list	No
Weakness	CWE-122
Published	2026-07-14
Last modified	2026-10-24

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-07-14 21:16 UTCPublished CVE record published
2026-10-24 21:10 UTCUpdated Record last modified

google chrome UPGRADE

Affected: < 150.0.7871.125

Fixed in: 150.0.7871.125

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.125 (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-15767?

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

Is CVE-2026-15767 being exploited?

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

CVE-2026-15767 affects chrome. Severity is high (CVSS 8.8). Heap buffer overflow in libyuv in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted video file. (Chromium security severity: High)

How urgent is CVE-2026-15767?

Priority 40/100. High severity

Software pages

Windows vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-15764 HIGH 7.5 UPGRADE Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.125 allowed a remote attacker who convin
CVE-2026-15776 HIGH 8.8 UPGRADE Inappropriate implementation in V8 in Google Chrome prior to 150.0.7871.125 allowed a remote attacker to execu
CVE-2026-15773 CRITICAL 9.6 UPGRADE Use after free in Core in Google Chrome on Windows prior to 150.0.7871.125 allowed a remote attacker to potent
CVE-2026-15769 HIGH 8.3 UPGRADE Insufficient validation of untrusted input in Linux Toolkit Theming in Google Chrome on Linux prior to 150.0.7
CVE-2026-15765 HIGH 7.5 UPGRADE Use after free in Ozone in Google Chrome prior to 150.0.7871.125 allowed a remote attacker who convinced a use

References

← Back to latest CVEs