Chrome is ubiquitous; origin-policy bypass can expose cross-site data from many users and enterprise web apps, warranting broad IT notification.
CVE-2026-91719
Chrome XML code injection bypasses same-origin, enabling cross-origin data access.
Is CVE-2026-91719 being exploited?
Not confirmed. CVE-2026-91719 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.
How severe is CVE-2026-91719?
CVE-2026-91719 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-91719?
Yes. A fix has been recorded for CVE-2026-91719. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91719 affect?
CVE-2026-91719 affects Google Chrome < 153.0.8010.47 (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91719?
Update Chrome to 153.0.8010.47 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted HTML/XML can bypass same-origin policy, enabling remote code injection and cross-origin data access/exfiltration in users' browsers.
Immediate action required
- affected< 153.0.8010.47
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.