dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 18 Jun 2024.
ChromeWeb browser · Google

CVE-2024-5274

CRITICAL · 9.6 CVSS v3.1 Published 2024-05-28
Fix available
A fix is available. Upgrade to 125.0.6422.112 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
Type Confusion in V8 in Google Chrome prior to 125.0.6422.112 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

A type confusion vulnerability in Google Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code inside a sandbox via a maliciously crafted HTML page. This occurs when the V8 engine incorrectly handles object type assumptions, potentially leading to memory corruption and sandbox escape.

MitigationUpdate Google Chrome to version 125.0.6422.112 or later to patch the V8 type confusion vulnerability.

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:< 125.0.6422.112
FedoraOperating system
Affected:= 39= 40

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Google Chrome version
    Navigate to chrome://settings/help in the browser address bar, or run 'google-chrome --version' from command line
    Affected if The displayed version is earlier than 125.0.6422.112 (e.g., 125.0.6422.71, 124.x.x.x, etc.)
  2. Check Chrome package version on Linux
    Run 'google-chrome --version' or check the package manager (dpkg -l google-chrome-stable or rpm -qi google-chrome-stable)
    Affected if The installed package version is less than 125.0.6422.112
  3. Verify Chrome installation path
    Confirm the Chrome binary being used is the standard Google Chrome installation (not a bundled version in another application)
    Affected if The browser is a standard Google Chrome installation and version check shows it is below 125.0.6422.112
  4. Check Chromium-based browsers separately
    If using other Chromium-based browsers (Brave, Edge, etc.), check their version separately in their own about pages or via their command-line flags
    Affected if A Chromium-based browser is in use and its version is derived from a Chrome build earlier than 125.0.6422.112

You are affected if the installed Google Chrome version (or a Chromium-based browser using the same V8 engine version) is earlier than 125.0.6422.112.

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

Update Google Chrome to version 125.0.6422.112 or later to patch the V8 type confusion vulnerability.

Recommended fix High confidence

Chrome 125.0.6422.112 or later; Fedora systems should update to latest chromium/google-chrome packages available in the Fedora repositories

  1. Update Google Chrome to version 125.0.6422.112 or later. On Linux systems, this is typically done through your package manager (e.g., `sudo dnf update google-chrome-stable` on Fedora, or `sudo apt update && sudo apt upgrade google-chrome-stable` on Debian/Ubuntu)
  2. For Fedora 39 and 40 systems, ensure all system security updates are applied: run `sudo dnf update` or `sudo dnf upgrade` to receive the latest Chrome/chromium security patches
  3. Restart the browser after updating to ensure the new version is fully loaded
  4. Verify the Chrome version by navigating to chrome://settings/help to confirm you are on 125.0.6422.112 or higher
Caveat Chrome stable channel updates generally have no breaking changes; this is a security-only update

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
4.0 hours of engineering $750
Get it fixed fast

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5274 — 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-5274 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