CVE-2026-14382 in Google Chrome ANGLE
Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Quick answer
Google Chrome should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Google Chrome before 150.0.7871.46
Fixed versions
- Google Chrome 150.0.7871.46 or later
- Google Chrome 150.0.7871.46/.47 or later on Windows and Mac
How to fix it
CVE-2026-14382 affects Google Chrome. The issue means a crafted page may help escape the browser sandbox. Treat it as a priority if this software is reachable by users, admins, browsers, or the network. Update to Google Chrome 150.0.7871.46 or later, or follow the linked vendor advisory if your branch needs a backport.
- Inventory every Google Chrome install, package, server, browser, or managed device in use.
- Compare installed versions with the affected range: Google Chrome before 150.0.7871.46.
- Update to Google Chrome 150.0.7871.46 or later.
- If you cannot update today, restrict access to trusted users and trusted networks only.
- Review logs for crashes, failed requests, privilege changes, unusual data access, or exploit alerts.
- Rotate secrets, tokens, and passwords if exposure or abuse is suspected.
- Document the update and keep the advisory link with the change record.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version matches the fixed guidance: Google Chrome 150.0.7871.46 or later; Google Chrome 150.0.7871.46/.47 or later on Windows and Mac.
- Confirm risky admin, API, browser, or network exposure is reduced.
- Retest the affected workflow after the update or mitigation.
- Review logs again after patching for repeated suspicious activity.
- Run a new Fixnx scan where the affected software is part of the public site.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-14382?
Google Chrome versions listed as affected should be reviewed: Google Chrome before 150.0.7871.46.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.