PatchSiren cyber security CVE debrief
CVE-2026-91719 Google CVE debrief
A code injection vulnerability in XML in Google Chrome prior to 153.0.8010.47 allows remote attackers to bypass web origin policy via crafted HTML pages. This issue, tracked as CVE-2026-91719, was publicly disclosed on September 15, 2026, and last modified on September 18, 2026. The vulnerability has a CVSS score of 8.1, indicating high severity. Defenders should assess exposure and prioritize updating Google Chrome to version 153.0.8010.47 or later. The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions.
- Vendor
- Product
- Chrome
- CVSS
- HIGH 8.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-15
- Original CVE updated
- 2026-09-18
- Advisory published
- 2026-09-15
- Advisory updated
- 2026-09-18
Who should care
Defenders responsible for managing Google Chrome deployments, as well as security teams focused on web browser security, should assess exposure and prioritize updating Google Chrome to version 153.0.8010.47 or later.
Why it matters
CVE-2026-91719 is a code injection vulnerability in XML in Google Chrome that allows remote attackers to bypass web origin policy. Defenders should prioritize verifying and applying the update, assessing exposure, and monitoring for potential bypass attempts.
- Defenders need to verify and apply updates to Google Chrome to prevent potential bypass of web origin policy.
- Security teams must assess exposure in their environment, focusing on systems and users that interact with Google Chrome.
- The vulnerability's high CVSS score indicates a significant risk that defenders should address promptly.
Technical summary
The vulnerability, CVE-2026-91719, is a code injection issue in XML in Google Chrome prior to version 153.0.8010.47. This allows remote attackers to bypass web origin policy via crafted HTML pages. The CVSS score for this vulnerability is 8.1, indicating a high severity level.
Defensive priority
Defenders should prioritize verifying and applying the update to Google Chrome, ensuring that the version is 153.0.8010.47 or later, and assess exposure in their environment.
Recommended defensive actions
- Verify and apply the update to Google Chrome, ensuring that the version is 153.0.8010.47 or later.
- Assess exposure in the environment, focusing on systems and users that interact with Google Chrome.
- Monitor for potential bypass attempts of web origin policy in Google Chrome.
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish specific exploitation instances or impacts, requiring verification from official sources.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-91719 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-91719
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-91719 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-91719
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0541751186.html
[email protected] - Release Notes, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://issues.chromium.org/issues/542115030
[email protected] - Permissions Required
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.