CSP bypass via Loader policy enforcement failure
Published Jun 24, 2025 · Updated Feb 26, 2026
Insufficient policy enforcement in Google Chrome's Loader before 138.0.7204.49 allows remote attackers to bypass CSP via crafted HTML. Google identifies the Loader as the faulty component but has not published which policy check is omitted or incorrectly applied to attacker-controlled content. User interaction is required to load the crafted page; published evidence establishes neither arbitrary code execution nor availability impact.
Summary
What happened
Insufficient policy enforcement in Google Chrome's Loader before 138.0.7204.49 allows remote attackers to bypass CSP via crafted HTML. Google identifies the Loader as the faulty component but has not published which policy check is omitted or incorrectly applied to attacker-controlled content. User interaction is required to load the crafted page; published evidence establishes neither arbitrary code execution nor availability impact.
The record
- CVE
- CVE-2025-6556
- Published
- Jun 24, 2025
- Updated
- Feb 26, 2026
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-288, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 24, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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=138.0.7204.49 <138.0.7204.49
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.
Weakness, pattern, technique
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