dbcve.org
ChromeWeb browser · Google

CVE-2024-5838

HIGH · 8.8 CVSS v3.1 Published 2024-06-11
Fix available
A fix is available. Upgrade to 126.0.6478.54 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
Type Confusion in V8 in Google Chrome prior to 126.0.6478.54 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

Type confusion vulnerability in Chrome's V8 JavaScript engine that allows a remote attacker to perform out-of-bounds memory access via a malicious HTML page. The flaw exploits the type system to cause incorrect object handling leading to memory corruption.

MitigationUpdate Google Chrome to version 126.0.6478.54 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:< 126.0.6478.54
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
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 Linux: rpm -qa | grep google-chrome or dpkg -l | grep chrome. On Windows: Check Program Files/Google/Chrome/Application/ folder or Registry. On macOS: Check /Applications/ for Google Chrome.app
    Affected if Chrome browser is present on the system
  2. Determine installed Chrome version
    On Linux terminal: google-chrome --version or rpm -q google-chrome. In browser: Navigate to chrome://settings/help
    Affected if Version number is lower than 126.0.6478.54
  3. Verify Chrome is in use
    Check if Chrome is the default browser or commonly used browser; look for running Chrome processes: ps aux | grep chrome or tasklist | grep chrome on Windows
    Affected if Chrome is actively used to browse web pages (vulnerability triggers when visiting malicious HTML pages)
  4. Check Fedora package version (if applicable)
    On Fedora systems: rpm -qa | grep -i chrome to list installed Chrome packages, then rpm -q --queryformat '%{VERSION}-%{RELEASE} ' <package-name> for full version
    Affected if Running Fedora 39 or 40 with Chrome version below 126.0.6478.54

You are affected if Google Chrome is installed with a version lower than 126.0.6478.54 and the browser is used to access web 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 126.0.6478.54 or later
Fixed in 126.0.6478.54
Interim mitigation

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

Recommended fix High confidence

Chrome 126.0.6478.54 or later; Fedora Chromium packages via dnf update

  1. For Chrome Desktop users: Navigate to chrome://settings/help and click 'Update Google Chrome', or download version 126.0.6478.54 or later from the official Chrome release channel
  2. For Fedora systems: Run 'sudo dnf update chromium' or 'sudo dnf update' to receive the patched Chromium package for Fedora 39 or 40
  3. Restart the browser after updating to apply the fix
  4. Verify the version by navigating to chrome://version - confirm version is 126.0.6478.54 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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