CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 10 November 2026, catalog version 2026.11.10. It is a use-after-free in Chromium's XML component, and CISA's description says it could allow a remote attacker to execute arbitrary code inside the sandbox via a specially crafted webpage — which means a single page load is the entire attack surface. Because the flaw sits in Chromium rather than in one vendor's product, it reaches Google Chrome, Microsoft Edge, Opera and other browsers built on the same engine. The fix is the vendor's patched build, and the remediation due date is 2026-11-24.
What CVE-2026-125350 actually is
It is a memory-lifetime bug, not a configuration mistake. A use-after-free means a block of memory is released while something still holds a pointer into it; if an attacker can influence what gets written into that reused block, they can redirect execution rather than merely crash the tab. CISA places the flaw in the XML component — the part of the browser that parses markup arriving from the network, which is exactly the input an attacker controls. The description adds that code execution happens inside the sandbox, so process isolation limits the damage but does not exempt you from patching. What the advisory does not specify: the affected build ranges, who reported the flaw, or whether public exploit code exists. Known ransomware campaign use is listed as unknown.
Which browsers are in scope
Anything Chromium-based is in scope; Chrome is simply the one everyone remembers. CISA's description names Google Chrome, Microsoft Edge and Opera, and explicitly says that list is not exhaustive. That detail matters for asset inventories that record a single line item called Chrome and stop there — an Edge install on a finance laptop and an Opera install on a marketing machine carry the same exposure. The advisory does not enumerate embedded Chromium runtimes inside desktop applications, so treat those as unconfirmed and ask the vendor rather than assuming either way. If your software catalogue is assembled from one browser's telemetry, this is the week to widen it; how we think about system inventories covers what that looks like in practice.
The next 24 hours: patch, verify, watch the logs
Push the patched build to every managed browser today, then prove which version is actually serving traffic. CISA's required action is to apply mitigations in accordance with vendor instructions, and the clock stops on 2026-11-24.
- Update Google Chrome, Microsoft Edge and Opera through their own release channels, not only through your OS patch ring — browsers ship on their own cadence and often lag in managed fleets.
- Verify on the endpoint by reading the browser's About page or chrome://version, then compare that reported build against the fixed build named in the vendor's release notes.
- Spot-check the machines your MDM already labels compliant. Deployed and running-after-next-restart are different states, and laptops that sleep for days sit in the gap.
- After the update, watch for renderer crash clusters, unexpected child processes, and outbound connections that appear within seconds of a page load.
Keep the version check in your release checklist rather than in a wiki page nobody opens.
Why this is a BOD 26-04 item, not just a browser update
CISA routes the required action through BOD 26-04, so this patch inherits a directive's paperwork, not just a browser team's backlog. The entry asks for mitigations in line with vendor instructions while ensuring compliance with BOD 26-04, Prioritizing Security Updates Based on Risk, and with CISA's Forensics Triage Requirements; for cloud services, follow the same guidance or discontinue use of the product if mitigations are unavailable. It also pushes the judgement onto the asset owner: evaluate each asset's internet exposure and apply the patching guideline accordingly. For a private company the useful translation is simpler than the directive reads. A browser on a laptop that opens arbitrary links is internet-exposed and goes first; a locked kiosk on an isolated network is less exposed and can be sequenced behind it — but it still gets patched.
What AI changes about finding bugs like this
AI-assisted review makes this class of bug cheaper to catch on a first pass, and easier to drown in false positives. A use-after-free in a parser is a lifetime problem: memory is freed on one path and used on another, often hundreds of lines apart, which is precisely the distance human review is worst at holding in working memory. A model asked to trace ownership across an error path will surface candidates a tired reviewer skips, and it will do it across every parser entry point in a morning. The catch is triage — expect most candidates to be noise, and keep the ground truth in tooling: address sanitizers in CI, fuzzing on parse routines, and regression tests on anything that gets fixed. To be clear, CISA's description says nothing about how CVE-2026-125350 was discovered, and this is not a claim that AI found it.
Where to start
The order of work is unglamorous: widen the inventory past Chrome, patch by 2026-11-24, and add a check that reads the browser version actually running rather than the version your deployment log recorded. If your dashboards cannot answer which build is live on a given machine, that gap will cost you more than this one CVE — it is the same gap that slows down a cloud or endpoint audit and the same one that shows up when you roll out an internal tool. Maysan Labs builds the dashboards and internal tooling that close it; what we do is the place to look if that is on your list this quarter.
Buying software or a website?
Twelve questions to ask any vendor before you sign: price, your data, fit for an Indian business and support.
Get the free checklistWritten by Maysan Engineering Team at Maysan Labs, a software studio in Gurgaon, India. Follow us on LinkedIn