# CVE-2026-15767: Google Chrome heap buffer overflow in libyuv

Source: https://junglewise.ai/threats/cve-2026-15767-google-chrome-heap-buffer-overflow-in-libyuv  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-14. Updated: 2026-07-14  
License: CC BY 4.0 with a link back

CVE-2026-15767 · Severity: high · CVSS 8.8 · Published 2026-07-14

A security vulnerability exists in Google Chrome for Windows that could allow a remote attacker to execute malicious code. The issue occurs when the browser processes a specially crafted video file, potentially compromising the user's system. Users are advised to update to the latest version of Chrome to mitigate this risk.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-15767 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-15767 being exploited in the wild.

**How severe is CVE-2026-15767?** High severity, with a CVSS score of 8.8, published 14 July 2026.

**Which products and versions are affected?** Google Chrome prior to 150.0.7871.125.

**Is there a fix for CVE-2026-15767?** A patch was published on 2026-07-14: Fixed in version 150.0.7871.125 for Windows Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-15767 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-15767?** Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A heap-based buffer overflow (CWE-122) exists in the libyuv library within Google Chrome for Windows. The vulnerability is triggered when the browser processes a maliciously crafted video file. A remote, unauthenticated attacker can exploit this flaw by enticing a user to visit a malicious website or open a malicious video, leading to arbitrary code execution within the browser's sandbox environment. The issue was addressed in Chrome version 150.0.7871.125.

## Affected products

- Google Chrome prior to 150.0.7871.125

## Timeline

- 2026-05-19: disclosed: Reported by Google internal researchers
- 2026-07-14: patched: Fixed in version 150.0.7871.125 for Windows
- 2026-07-14: advisory

## References

- [https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.html](https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.html)
- [https://issues.chromium.org/issues/514748734](https://issues.chromium.org/issues/514748734)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)