Access-control bypass via crafted HTML
Published Jun 11, 2024 · Updated Mar 13, 2025
Policy bypass in CORS in Google Chrome before 126.0.6478.54 allows remote attackers to bypass discretionary access control via crafted HTML. The public advisory names the CORS component, but the Chromium issue requires sign-in and no public source identifies the faulty check or code path. Exploitation requires a user to load attacker-controlled HTML and permits unauthorized cross-origin actions, with no reported data disclosure or service interruption.
Summary
What happened
Policy bypass in CORS in Google Chrome before 126.0.6478.54 allows remote attackers to bypass discretionary access control via crafted HTML. The public advisory names the CORS component, but the Chromium issue requires sign-in and no public source identifies the faulty check or code path. Exploitation requires a user to load attacker-controlled HTML and permits unauthorized cross-origin actions, with no reported data disclosure or service interruption.
The record
- CVE
- CVE-2024-5840
- Published
- Jun 11, 2024
- Updated
- Mar 13, 2025
- Vendor
- Fedora Project
- Product
- Fedora Linux
- Classifications
- CWE-284, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2024CVE publishedPublication date reported by the CVE source.
- Mar 13, 2025Record 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=39
- Affected versionversion=40
What conditions does exploitation require?
What is affected?
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