dbcve.org
ChromeWeb browser · Google

CVE-2024-5846

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
Use after free in PDFium in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: Medium)

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

Use-after-free vulnerability in PDFium (Google Chrome's PDF rendering engine) allows a remote attacker to exploit heap corruption by tricking a user into opening a specially crafted malicious PDF file. This memory corruption can potentially lead to arbitrary code execution.

MitigationUpdate Google Chrome to version 126.0.6478.54 or later. Organizations should deploy the update through their patch management systems and verify PDF functionality post-update.

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. Identify installed Google Chrome version
    On Windows: Open Chrome, go to Menu > Help > About Google Chrome. On Linux: Run 'google-chrome --version' or 'chromium-browser --version' in terminal. On macOS: Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' or click Chrome > About Google Chrome menu.
    Affected if The displayed version number is less than 126.0.6478.54 (e.g., 126.0.6478.53 or earlier)
  2. Check Chrome installation source on Fedora
    Run 'rpm -qa | grep -i chrome' or 'dnf list installed | grep -i chrome' to list installed Chrome-related packages.
    Affected if Google Chrome is installed from Fedora repositories on Fedora 39 or 40 systems, as these versions are listed as affected
  3. Verify Chrome is default PDF viewer
    Inspect system settings: On Windows/Linux, check default applications for PDF files. On Linux, run 'xdg-mime query default application/pdf'.
    Affected if Google Chrome or Chromium is set as the default application to open PDF files, enabling automatic PDFium processing of untrusted PDFs
  4. Check for recent Chrome process memory anomalies
    Review Chrome crash reports in 'chrome://crashes' address bar, or check system event logs for Chrome-related crashes around the time of opening PDFs.
    Affected if Frequent or unusual crashes occur when viewing PDF files, which may indicate exploitation attempts

A system is affected if Google Chrome versions prior to 126.0.6478.54 are installed and users can open PDF files using Chrome's built-in PDF viewer.

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. Organizations should deploy the update through their patch management systems and verify PDF functionality post-update.

Recommended fix High confidence

Chrome 126.0.6478.54 or later

  1. Check the current Google Chrome version by navigating to chrome://settings/help
  2. If Chrome version is less than 126.0.6478.54, update Chrome by clicking 'Update Google Chrome' and restarting the browser
  3. Alternatively, download and install Chrome 126.0.6478.54 or later from the official Google Chrome website (google.com/chrome)
  4. For Fedora systems, run 'sudo dnf update google-chrome-stable' to ensure the patched version is installed
  5. Restart Chrome after updating to apply the security fix

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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