CISA added an actively exploited flaw in Chromium’s XML component to its Known Exploited Vulnerabilities catalog on November 10. A crafted webpage can trigger the use-after-free and run code inside the browser sandbox. People browsing the web with affected Chrome builds are exposed; CISA also names Microsoft Edge and Opera as Chromium-based browsers that could be affected.
Chrome’s own CVE record identifies builds before 157.0.8103.50 as affected. This gives endpoint teams a concrete version to verify on Chrome, while the other browser makers’ applicable builds need to be checked against their own updates. Google’s desktop Stable Channel update is the vendor release referenced by both CISA and the CVE record.
A webpage reaches the XML parser
A user has to load the crafted HTML page. Chrome then processes its XML content, and the use-after-free lets the remote attacker execute code in the sandbox. The Chrome CNA describes the issue as: “Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page.” It rates the Chromium security severity High and classifies the weakness as CWE-416.
A use-after-free means a program keeps using memory after it has released it. In this case, the defect sits in the XML component reached from web content. The documented execution scope is the browser sandbox, the containment layer around code that processes an untrusted page. Treat operating-system compromise as a separate finding that needs its own evidence while you patch the page-to-XML path.
Browsers share code, not release numbers
CISA’s entry includes Chrome, Edge and Opera in the potentially affected Chromium browser family. Chrome’s 157.0.8103.50 threshold comes from the Chrome CNA record; use each other vendor’s advisory to identify its applicable update. A fleet count based only on the Chrome binary can miss a second Chromium-based browser on the same machine.
CISA marks the vulnerability as known exploited and sets November 24 as the remediation due date in the KEV entry. Its ransomware-use field reads “Unknown.” The catalog gives teams a patching priority, while an endpoint version inventory tells them which installed browsers still need work. For exploitation recognition, investigate relevant browser or endpoint alerts under normal incident-response procedures; the available advisories offer no exploit-specific indicator.
Install, restart, verify the browser
Update managed Chrome installations to at least 157.0.8103.50, then restart the browser so the running process uses the updated build. Check the version in Chrome’s About page and compare it with the endpoint software inventory; investigate machines whose browser process remains on an older build after deployment. Scope Edge, Opera and any other Chromium-derived browser in your fleet against that vendor’s fix, without applying the Chrome version number to them.
For agencies covered by CISA’s KEV requirements, track the November 24 due date and follow the vendor and CISA guidance linked in the catalog. For everyone else, the same inventory-to-running-version comparison is the useful test: after rollout and restart, the affected Chrome process should report 157.0.8103.50 or newer. That test measures the patch actually loaded, not just an update job marked complete.