Is CVE-2026-103628 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-103628 being exploited in the wild.

How severe is CVE-2026-103628?

Critical severity, with a CVSS score of 9.6, published 2 October 2026.

Which products and versions are affected?

Google Chrome prior to 154.0.8037.97.

Is there a fix for CVE-2026-103628?

Yes: fixed in Chrome 154.0.8037.97. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-103628 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-103628?

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.

CVE-2026-103628: Google Chrome out-of-bounds write in WebGL

CVE-2026-103628 · Severity: critical · CVSS 9.6 · Published 2026-10-02

Google Chrome's WebGL graphics renderer contains a critical memory corruption bug that can be triggered by viewing a specially crafted webpage. An attacker can exploit this to execute arbitrary code outside the browser sandbox, gaining full system compromise without the browser's security protections.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-103628 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-103628 being exploited in the wild.
How severe is CVE-2026-103628?: Critical severity, with a CVSS score of 9.6, published 2 October 2026.
Which products and versions are affected?: Google Chrome prior to 154.0.8037.97.
Is there a fix for CVE-2026-103628?: Yes: fixed in Chrome 154.0.8037.97. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-103628 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-103628?: 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.

How to fix

Fixed in: Chrome 154.0.8037.97

Technical details

An out-of-bounds write vulnerability in Chrome's WebGL implementation allows an unauthenticated remote attacker to write beyond allocated memory boundaries via a crafted HTML page. The vulnerability bypasses the sandbox isolation, enabling arbitrary code execution with browser process privileges. No user interaction beyond viewing a malicious webpage is required.

Affected products

Google Chrome prior to 154.0.8037.97

Timeline

2026-10-02: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.