CVE-2026-106247: Buffer overflow in ANGLE

Published Jun 16, 2026
·
Updated

Buffer overflow in ANGLE in Google Chrome prior to 155.0.8059.39 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)

Other sources

Chromium CVE-2026-106247: Buffer overflow

— Microsoft

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.

— Microsoft

Credit

Google

Affected Software

3 affected componentsFixes available
Google Chrome<155.0.8059.39
155.0.8059.39
Google Chrome<155.0.8059.39
Microsoft Edge (Chromium-based)<155.0.4283.45
155.0.4283.45

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 155.0.4283.45
  3. Upgrade

    Upgrade Google Chrome to a version that resolves this vulnerability.

    Fixed in 155.0.8059.39

Event History

Jun 16, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Oct 6, 2026
CVE Published
via MITRE·06:41 PM
Data Sourced
via MITRE·06:41 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 16, 2026
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

Which Chrome versions need to be updated?

Google Chrome versions prior to 155.0.8059.39 are affected according to the provided advisory.

2

What must an attacker achieve before this issue can be exploited?

The attacker must already have compromised the Chrome renderer process. Exploitation also involves a crafted HTML page, and the CVSS vector indicates user interaction is required.

3

Does this vulnerability enable escape from Chrome's sandbox?

Yes. A successful exploit could allow arbitrary code execution outside the sandbox after renderer compromise.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203