CVE-2025-1914: Google Chrome · Out of bounds read
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 134.0.6998.35 soon.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 134.0.6998.35
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 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 134.0.6998.35.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
To mitigate CVE-2025-1914, organizations should immediately update all Google Chrome installations to version 134.0.6998.35 or later once the patch is officially released. Until then, consider implementing the following measures: 1) Employ web filtering solutions to block access to known malicious websites and suspicious domains that could host exploit pages. 2) Use endpoint protection platforms with behavior-based detection to identify and block exploitation attempts targeting the browser. 3) Educate users about the risks of visiting untrusted websites and clicking on unknown links to reduce the likelihood of triggering the vulnerability. 4) Enable sandboxing and strict site isolation features in Chrome to limit the impact of potential exploitation. 5) Monitor network traffic for unusual patterns indicative of exploitation attempts. 6) For high-security environments, consider temporarily restricting browser usage or deploying alternative browsers until patches are applied. 7) Maintain an up-to-date inventory of browser versions across the organization to ensure timely patch management. These targeted actions complement the critical step of applying the vendor patch promptly.
Description
Out of bounds read in V8 in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)