Chromium use-after-free flaw in XML component exploited, added to CISA catalogue
On 10 November 2026, CISA added Google Chromium vulnerability CVE-2026-125350 to its catalogue of actively exploited flaws. It affects Chromium-based browsers including Chrome, Edge and Opera, which covers almost every workstation.
What to do now
- Product
- Google Chromium (Chrome, Microsoft Edge, Opera and other Chromium-based browsers)
- Affected versions
- Versions not stated in the source; Chromium-based browsers including Chrome, Edge and Opera.
- Fixed in
- Not stated; the source references Google's November 2026 Chrome stable channel desktop update.
- CVE
- CVE-2026-125350
The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-125350 to its Known Exploited Vulnerabilities catalogue on 10 November 2026. The bug is a use-after-free (CWE-416) in the XML component of Google Chromium.
A remote attacker can trigger it by getting a user to load a specially crafted web page, which allows arbitrary code execution inside the browser sandbox. The sandbox limits what the attacker can reach directly, but flaws of this kind are frequently chained with a separate sandbox escape.
Google Chrome is not the only browser in scope. CISA notes that multiple Chromium-based browsers may be affected, including Microsoft Edge and Opera, and that the list is not exhaustive.
The CISA entry points to a Chrome stable channel update for desktop released by Google in November 2026. The source does not list the vulnerable versions or the fixed version number, so administrators should check Google's release notes and the advisories of other browser vendors. Whether the flaw has been used in ransomware campaigns is listed as unknown.
US federal civilian agencies must remediate by 24 November 2026. Other organisations should work to at least the same deadline, and ideally sooner, given that exploitation has already been observed.
What to do now
- Roll out the November 2026 Chrome stable channel desktop update from Google now and make sure browsers are restarted so the fix takes effect.
- Check for and install vendor updates for every other Chromium-based browser in your environment, such as Microsoft Edge and Opera.
- Use your endpoint management tooling to confirm that all machines run the fixed version listed in each vendor's advisory.
- As general good practice, review endpoint and web proxy logs for unusual browser process behaviour.