Google has confirmed a high-severity use-after-free vulnerability within the Chromium engine, identified as CVE-2026-125350. The flaw resides in the browser’s XML component and poses a significant security risk, as it could enable a remote attacker to execute arbitrary code within the browser sandbox by enticing a user to visit a specially crafted webpage.
The vulnerability is confirmed to be under active exploitation in the wild. Multiple threat intelligence and government tracking sources, including the Cybersecurity and Infrastructure Security Agency (CISA) Known Exploited Vulnerabilities catalog, the European Union Agency for Cybersecurity (ENISA) EUVD, and commercial research firm VulnCheck, have formally listed the flaw as being actively leveraged by malicious actors.
Evidence indicates that the exploitation of this vulnerability occurred prior to its official disclosure. While the CVE record was published on November 10, 2026, and reserved on November 9, 2026, reports of active exploitation emerged as early as November 9. This timeline suggests that attackers were utilizing the exploit in real-world scenarios at least one day before the vulnerability was publicly acknowledged and documented.
Because the vulnerability affects the underlying Chromium engine, the risk extends beyond the Google Chrome browser. Any software or web browser built upon the Chromium framework—including Microsoft Edge and Opera—may be susceptible to the same attack vector. Users and administrators of these platforms are advised to monitor for updates from their respective browser vendors to ensure they are running patched versions.
In response to the active exploitation, CISA has issued a directive requiring federal agencies to apply necessary mitigations in accordance with vendor instructions. This action falls under the agency’s BOD 26-04 mandate, which prioritizes security updates based on risk. Federal entities are tasked with evaluating the internet exposure of their assets and ensuring that patching guidelines are strictly followed.
For organizations and individual users, the primary defense remains the prompt application of security updates provided by browser manufacturers. If a patch is not immediately available for a specific Chromium-based product, stakeholders are advised to follow applicable BOD 26-04 guidance for cloud services or, in extreme cases, discontinue the use of the affected software until a fix is deployed.
While the technical details of the exploit remain limited, the classification of the flaw as a use-after-free error in the XML component highlights a critical memory management failure. Such vulnerabilities are frequently targeted because they can be weaponized to bypass security boundaries. The speed at which this vulnerability moved from discovery to active exploitation underscores the importance of rapid patch deployment in modern enterprise environments.
As of November 12, 2026, the vulnerability remains a high-priority item on security watchlists. Those responsible for organizational cybersecurity are encouraged to review their internal patch management processes to ensure compliance with the November 24, 2026, federal remediation deadline established by CISA.





