CVE-2025-6556: Google Chrome · Insufficient Policy Enforcement
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 138.0.7204.49 when convenient.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 138.0.7204.49
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade google/chrome to 138.0.7204.49.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Googlegoogle/chromepkg:deb/google/chromeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately ensure that all instances of Google Chrome are updated to version 138.0.7204.49 or later, where this vulnerability is addressed. Beyond patching, administrators should review and strengthen CSP implementations to minimize the impact of potential bypasses, including using nonce- or hash-based CSP directives rather than relying solely on source whitelisting. Employing browser security features such as Site Isolation and enabling strict HTTPS usage can reduce attack surface. User education to recognize and avoid suspicious links or websites is critical to mitigate risks requiring user interaction. Network-level protections, such as web filtering and intrusion detection systems, should be tuned to detect and block known malicious payloads or phishing attempts. Additionally, organizations should monitor for unusual browser behavior or indicators of compromise that might suggest exploitation attempts. Regular security assessments and penetration testing focusing on web application security can help identify residual risks related to CSP enforcement.
Description
Insufficient policy enforcement in Loader in Google Chrome prior to 138.0.7204.49 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Low)