dbcve.org
ChromeWeb browser · Google

CVE-2026-2649

HIGH · 8.8 CVSS v3.1 Published 2026-02-18
Fix available
A fix is available. Upgrade to 145.0.7632.109 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
Integer overflow in V8 in Google Chrome prior to 145.0.7632.109 allowed a remote attacker to potentially exploit heap corruption 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 · moderate confidence

Integer overflow vulnerability in the V8 JavaScript engine of Google Chrome allows remote attackers to corrupt heap memory via a maliciously crafted HTML page. This memory corruption could potentially enable arbitrary code execution or other exploits.

MitigationUpdate Google Chrome to version 145.0.7632.109 or later to patch the integer overflow vulnerability in V8.

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:< 145.0.7632.109

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 in the Chrome address bar and note the version number displayed, or go to chrome://settings/help
    Affected if The version number is lower than 145.0.7632.109 (for example, 145.0.7632.1 or earlier)
  2. Confirm V8 JavaScript engine is active
    V8 is Chrome's built-in JavaScript engine and is automatically enabled for all web browsing sessions. No manual configuration is needed.
    Affected if V8 is always active when Chrome is used to render web pages, making the integer overflow exploitable through any malicious HTML page
  3. Determine if Chrome is the primary browser
    Check if Google Chrome is installed on the system by looking for the Chrome application in Program Files (Windows) or Applications folder (Mac), or by running 'google-chrome --version' in terminal (Linux)
    Affected if Chrome is installed and used, regardless of whether it is the default browser

You are affected if Google Chrome is installed and its version is below 145.0.7632.109, since the vulnerable V8 JavaScript engine is always active when browsing with Chrome.

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.

From vendor data
Upgrade available Upgrade to 145.0.7632.109 or later
Fixed in 145.0.7632.109
Interim mitigation

Update Google Chrome to version 145.0.7632.109 or later to patch the integer overflow vulnerability in V8.

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-2026-2649 — 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-2026-2649 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