Skip to main content
CVE-2025-1918VulnerabilityPublished Updated

CVE-2025-1918: Google Chrome · Out of bounds read

Affects Google ChromeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 134.0.6998.35 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-26.

What to do

Upgrade Google Chrome to 134.0.6998.35.

Affected software

ProductAffectedFixed in
Google ChromeAffected
  • =134.0.6998.35
  • <134.0.6998.35
Fixed in
  • 134.0.6998.35

AI-suggested

1. Immediately update all Google Chrome installations to version 134.0.6998.35 or later to apply the official patch. 2. Implement network-level controls to block or quarantine suspicious PDF files, especially those received via email or downloaded from untrusted sources. 3. Employ endpoint security solutions capable of detecting and blocking malicious PDF payloads or anomalous PDF processing behaviors. 4. Educate users to avoid opening PDFs from unknown or untrusted sources and to report suspicious documents. 5. Where feasible, disable automatic PDF rendering or previewing in browsers and use dedicated PDF viewers with robust security controls. 6. Monitor security advisories and threat intelligence feeds for any emerging exploits targeting this vulnerability. 7. Conduct regular vulnerability assessments and penetration tests focusing on PDF handling components within the organization’s environment. 8. Apply principle of least privilege to browser processes and sandboxing features to limit the impact of potential exploitation.

Description

Out of bounds read in PDFium in Google Chrome prior to 134.0.6998.35 allowed a remote attacker to potentially perform out of bounds memory access via a crafted PDF file. (Chromium security severity: Medium)

References

Community reviews

Loading reviews…