CVE-2025-5064: Google Chrome · Inappropriate implementation
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium : upgrade to 137.0.7151.55 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 137.0.7151.55
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 27 May 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 2026-10-25.
What to do
Upgrade google/chrome to 137.0.7151.55.
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
European organizations should prioritize updating Google Chrome to version 137.0.7151.55 or later as soon as it becomes available to ensure the vulnerability is patched. If you cannot patch yet, organizations should implement the following mitigations: 1) Educate users about the risks of visiting untrusted or suspicious websites to reduce the likelihood of successful phishing attacks exploiting this vulnerability. 2) Employ web filtering solutions to block access to known malicious domains and suspicious URLs that could host crafted HTML pages exploiting this flaw. 3) Use Content Security Policy (CSP) headers to restrict the sources from which scripts and resources can be loaded, limiting the attack surface. 4) Monitor network traffic for unusual outbound requests that could indicate exploitation attempts. 5) Consider deploying browser isolation or sandboxing technologies to contain potential malicious activity within the browser environment. 6) Coordinate with IT and security teams to ensure rapid deployment of patches once available and to maintain up-to-date threat intelligence on this vulnerability.
Description
Inappropriate implementation in Background Fetch API in Google Chrome prior to 137.0.7151.55 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)