Content Security Policy bypass via crafted HTML
Published Sep 26, 2022 · Updated May 21, 2025
Content Security Policy bypass in Google Chrome before 105.0.5195.52 allows remote attackers to evade page restrictions via crafted HTML. The public record identifies insufficient policy enforcement in the browser's Content Security Policy handling but does not disclose the affected code path or exact validation error. A user must open attacker-controlled HTML; the demonstrated consequence is modification of behavior that the page's policy was intended to block.
Summary
What happened
Content Security Policy bypass in Google Chrome before 105.0.5195.52 allows remote attackers to evade page restrictions via crafted HTML. The public record identifies insufficient policy enforcement in the browser's Content Security Policy handling but does not disclose the affected code path or exact validation error. A user must open attacker-controlled HTML; the demonstrated consequence is modification of behavior that the page's policy was intended to block.
The record
- CVE
- CVE-2022-3056
- Published
- Sep 26, 2022
- Updated
- May 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-693, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 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=unspecified <105.0.5195.52
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