ChromeWeb browser · Google
CVE-2024-7965
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 · uneditedInappropriate implementation in V8 in Google Chrome prior to 128.0.6613.84 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 · high confidenceA heap corruption vulnerability exists in the V8 JavaScript engine in Google Chrome versions prior to 128.0.6613.84. A remote attacker can exploit this by tricking a user into visiting a specially crafted HTML page, potentially allowing arbitrary code execution or heap manipulation.
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
< 128.0.6613.84< 128.0.2739.42CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Note the version number displayed.Affected if The installed version is earlier than 128.0.6613.84 (e.g., 128.0.6613.83 or lower)
-
Check Microsoft Edge versionOpen Edge, click the three-dot menu > Help and feedback > About Microsoft Edge, or navigate to edge://settings/help. Note the version number displayed.Affected if The installed version is earlier than 128.0.2739.42 (e.g., 128.0.2739.41 or lower)
-
Confirm V8 engine contextNo separate check required - the V8 JavaScript engine is built into Chrome and Edge Chromium browsers by default. The vulnerability exists within this engine component.Affected if Using any vulnerable version of Chrome or Edge means the V8 engine contains the inappropriate implementation flaw
You are affected if you are running any version of Google Chrome below 128.0.6613.84 or Microsoft Edge Chromium below 128.0.2739.42, as both include the vulnerable V8 JavaScript engine.
Generated from the published advisory. Verify against your own configuration.
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 · scoped128.0.2739.42128.0.6613.84
Update Google Chrome to version 128.0.6613.84 or later to patch the V8 engine vulnerability.
Chrome 128.0.6613.84 or later; Edge Chromium 128.0.2739.42 or later
- For Google Chrome users: Navigate to chrome://settings/help and click 'Update Google Chrome', or download version 128.0.6613.84 or later from google.com/chrome
- For Microsoft Edge users: Navigate to edge://settings/help and click 'Update Microsoft Edge', or download version 128.0.2739.42 or later from microsoft.com/edge
- Restart the browser after updating to apply the fix
- Verify the installed version matches or exceeds the fixed release (Chrome: 128.0.6613.84, Edge: 128.0.2739.42)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7965 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-7965 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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