CVE-2025-5281: 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 26 Oct 2026, 09:08 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% 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 26 Oct 2026.
What to do
Upgrade Google Chrome to 137.0.7151.55.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
To mitigate this vulnerability effectively, European organizations should prioritize updating Google Chrome to version 137.0.7151.55 or later as soon as the patch becomes available. Until then, organizations can implement network-level protections such as web filtering to block access to known malicious or suspicious websites that could host crafted HTML pages exploiting this flaw. Deploying endpoint security solutions capable of detecting and blocking phishing attempts can reduce the likelihood of successful user interaction with malicious content. Additionally, organizations should conduct targeted user awareness training focusing on the risks of interacting with untrusted web content and recognizing phishing attempts. From a technical perspective, disabling or restricting BFCache usage via enterprise policies or browser configuration may be considered as a temporary workaround, although this could impact user experience. Monitoring browser telemetry and logs for unusual behavior related to navigation caching could help identify potential exploitation attempts. Finally, maintaining a robust incident response plan that includes browser vulnerability scenarios will enhance preparedness.
Description
Inappropriate implementation in BFCache in Google Chrome prior to 137.0.7151.55 allowed a remote attacker to potentially obtain user information via a crafted HTML page. (Chromium security severity: Medium)