Origin-policy bypass via missing CORS authorization
Published Sep 9, 2026 · Updated Sep 9, 2026
Missing authorization in CORS in Google Chrome before 153.0.8010.36 allows remote attackers to bypass web origin policy via crafted HTML. The public record identifies CORS as the affected locus but does not disclose which authorization check is omitted or which cross-origin operation proceeds unchecked. Exploitation requires prior renderer compromise and a crafted HTML page; the bounded consequence is bypass of web origin policy.
Summary
What happened
Missing authorization in CORS in Google Chrome before 153.0.8010.36 allows remote attackers to bypass web origin policy via crafted HTML. The public record identifies CORS as the affected locus but does not disclose which authorization check is omitted or which cross-origin operation proceeds unchecked. Exploitation requires prior renderer compromise and a crafted HTML page; the bounded consequence is bypass of web origin policy.
The record
- CVE
- CVE-2026-87434
- Published
- Sep 9, 2026
- Updated
- Sep 9, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-862, T1203
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 9, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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 versionversion=153.0.8010.36 <153.0.8010.36
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Public exploit references
No public exploit references are available in this record.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo