dbcve.org
ChromeWeb browser · Google

CVE-2025-1914

HIGH · 8.8 CVSS v3.1 Published 2025-03-05
Fix available
A fix is available. Upgrade to 134.0.6998.35 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds read vulnerability exists in the V8 JavaScript engine of Google Chrome versions prior to 134.0.6998.35. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, allowing the attacker to read memory outside allocated buffers.

MitigationUpdate Google Chrome to version 134.0.6998.35 or later. Organizations should deploy the update via their software distribution mechanisms.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 134.0.6998.35

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Navigate to chrome://version or about:version in the Chrome address bar and note the version number displayed
    Affected if The displayed version is lower than 134.0.6998.35 (for example, 133.0.6998.0 or earlier)
  2. Verify Chrome channel and build
    On chrome://version, confirm whether the installed build is Stable, Beta, Dev, or Canary. Also note the full version string including the build number
    Affected if Running any pre-134.0.6998.35 Stable, Beta, or Dev build exposes the V8 engine to this flaw
  3. Confirm V8 engine is in use
    The V8 JavaScript engine is always active when browsing web content in Chrome. No manual enablement check is required
    Affected if Any regular web browsing or execution of JavaScript in Chrome engages the vulnerable V8 component
  4. Assess user exposure to web content
    Determine whether users in the organization routinely visit untrusted or unfamiliar websites, as the attack requires a user to open a crafted HTML page
    Affected if Users who browse arbitrary web pages are at risk since the exploit triggers through malicious HTML/JavaScript content

An organization is affected if any installed Google Chrome version is below 134.0.6998.35 and users browse web content, as the vulnerable V8 JavaScript engine processes all such content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 134.0.6998.35 or later
Fixed in 134.0.6998.35
Interim mitigation

Update Google Chrome to version 134.0.6998.35 or later. Organizations should deploy the update via their software distribution mechanisms.

Recommended fix High confidence

Chrome 134.0.6998.35

  1. Open Google Chrome browser
  2. Navigate to Chrome menu (three dots) > Help > About Google Chrome, or directly visit chrome://settings/help
  3. Chrome will automatically check for available updates
  4. If version 134.0.6998.35 or later is available, click 'Update Google Chrome' or allow it to update automatically
  5. After the update completes, restart the browser to apply the changes
  6. Verify the installed version by returning to About Google Chrome to confirm version 134.0.6998.35 or newer is running

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1914 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1914 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data