Called exploited 1 days before disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE reserved
- CVE published1d
- First KEV listing1d
- Last KEV listing1d
- Last sightingsame day
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Nov 10, 2026
- EUVDENISA, European Unionlisted Nov 10, 2026
- VulnCheck KEVcommercial researchlisted Nov 9, 2026
- CIRCLaggregator, mirrors the abovelisted Nov 10, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationchromereleases.googleblog.com/2026/11/stable-channel-update-
- reported exploitationdocs.google.com/spreadsheets/d/1lkNJ0uQwbeC1ZTRrxdtuPLCIl7ml
3 public reports collected from VulnCheck and CIRCL, first on Nov 9, 2026. Each links to its original source. We have not verified them.
Description
Google Chromium contains a use-after-free vulnerability in the XML component that could allow a remote attacker to execute arbitrary code inside the sandbox via a specially crafted webpage. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
