CVE-2026-78905: Google ANGLE vulnerability

Q: Which systems should be prioritized for review?

Prioritize Google Chrome installations running a version earlier than 152.0.7977.65, because the affected ANGLE component is used by Chrome.

Q: How could an attacker trigger the issue?

An attacker could attempt exploitation remotely by causing a user to load a crafted HTML page. The reported impact is potential arbitrary code execution outside the sandbox.

Q: How can I determine whether an installation is affected?

Check the installed Google Chrome version. Versions prior to 152.0.7977.65 are affected according to the provided advisory information.

Published Aug 25, 2026

Updated

Type confusion in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Affected Software

1 affected component

Google ANGLE<152.0.7977.65

Event History

Aug 25, 2026

CVE Published

via MITRE·08:10 PM

Data Sourced

via MITRE·08:10 PM

DescriptionWeakness

Frequently Asked Questions

Which systems should be prioritized for review?

Prioritize Google Chrome installations running a version earlier than 152.0.7977.65, because the affected ANGLE component is used by Chrome.

How could an attacker trigger the issue?

An attacker could attempt exploitation remotely by causing a user to load a crafted HTML page. The reported impact is potential arbitrary code execution outside the sandbox.

How can I determine whether an installation is affected?

Check the installed Google Chrome version. Versions prior to 152.0.7977.65 are affected according to the provided advisory information.

CVE-2026-78905: Google ANGLE vulnerability

Affected Software

Event History

Frequently Asked Questions

Which systems should be prioritized for review?

How could an attacker trigger the issue?

How can I determine whether an installation is affected?

Company

Resources

Contact

Frequently Asked Questions

Which systems should be prioritized for review?

How could an attacker trigger the issue?

How can I determine whether an installation is affected?