Origin-policy bypass via XML script execution
Published Sep 15, 2026 · Updated Sep 15, 2026
Code injection in XML parsing in Google Chrome before 153.0.8010.47 allows remote attackers to bypass web origin policy via a crafted HTML page. DOMParser.parseFromString fails to mark XML script elements as already started, so scripts that should remain inert can execute after parsed content is inserted into a document. The attack requires a user to load attacker-controlled HTML; the documented consequence is a web-origin boundary bypass, not execution outside the browser sandbox.
Summary
What happened
Code injection in XML parsing in Google Chrome before 153.0.8010.47 allows remote attackers to bypass web origin policy via a crafted HTML page. DOMParser.parseFromString fails to mark XML script elements as already started, so scripts that should remain inert can execute after parsed content is inserted into a document. The attack requires a user to load attacker-controlled HTML; the documented consequence is a web-origin boundary bypass, not execution outside the browser sandbox.
The record
- CVE
- CVE-2026-91719
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- The fscrypt Project
- Product
- Chrome
- Classifications
- CWE-94, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected version<153.0.8010.47
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- XML DOMParser script-execution regression testproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us