dbcve.org
ChromeWeb browser · Google

CVE-2024-12695

HIGH · 8.8 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 131.0.6778.204 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 write in V8 in Google Chrome prior to 131.0.6778.204 allowed a remote attacker to execute arbitrary code inside a sandbox 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 write vulnerability in Google Chrome's V8 JavaScript engine (prior to version 131.0.6778.204) allows remote attackers to achieve arbitrary code execution through a maliciously crafted HTML page. The vulnerability is rated high severity due to the ability to break out of V8's memory protections, though code execution occurs within Chrome's sandbox.

MitigationUpdate Google Chrome to version 131.0.6778.204 or later to remediate this vulnerability. Organizations should push the update via enterprise management tools and verify compliance.

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

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 if Google Chrome is installed
    On Windows: Look for Chrome in Program Files or check Start Menu. On Mac: Check /Applications/ for Google Chrome.app. On Linux: run 'which google-chrome' or check common installation directories.
    Affected if Google Chrome is present on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or from command line run 'google-chrome --version' (Linux) or check the executable properties (Windows). On Mac, run: defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString
    Affected if Unable to determine version indicates Chrome may not be standard install
  3. Compare version against vulnerable range
    Compare the installed version number to 131.0.6778.204. Any version less than 131.0.6778.204 is affected (for example: 131.0.6778.108, 131.0.6778.139, 130.x.x.x, etc.)
    Affected if Installed version is less than 131.0.6778.204 (for example: 131.0.6778.108 < 131.0.6778.204)
  4. Verify V8 engine is in use
    The V8 JavaScript engine is built into Chrome and always active for JavaScript execution in the browser. No additional configuration check needed - if Chrome is running, V8 is processing JavaScript.
    Affected if Chrome is used to browse web pages with JavaScript enabled (the default state)

You are affected if Google Chrome is installed with any version lower than 131.0.6778.204, as the V8 JavaScript engine vulnerability can be triggered when visiting a crafted HTML page.

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 131.0.6778.204 or later
Fixed in 131.0.6778.204
Interim mitigation

Update Google Chrome to version 131.0.6778.204 or later to remediate this vulnerability. Organizations should push the update via enterprise management tools and verify compliance.

Recommended fix High confidence

131.0.6778.204 or later

  1. Open Google Chrome browser
  2. Navigate to chrome://settings/help or click Help > About Google Chrome
  3. Chrome will automatically check for updates
  4. If update 131.0.6778.204 or later is available, click 'Update Google Chrome'
  5. Restart the browser to complete the update

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-2024-12695 — 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-2024-12695 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