ChromeWeb browser · Google
CVE-2024-5834
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 Dawn in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to execute arbitrary code 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 confidenceInappropriate implementation in Dawn (Google's WebGPU rendering framework) in Google Chrome prior to version 126.0.6478.54 allows a remote attacker to achieve arbitrary code execution through a maliciously crafted HTML page that triggers the vulnerable WebGPU code path.
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
< 126.0.6478.54
FedoraOperating system
= 39= 40CVSS 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 installed Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the installed version numberAffected if Version is less than 126.0.6478.54 (e.g., 126.0.6478.53 or earlier)
-
Verify WebGPU is accessibleIn Chrome, navigate to chrome://gpu or check if WebGPU appears in the Graphics Feature Status section. Alternatively, visit a WebGPU demo site to confirm the API is functionalAffected if WebGPU is listed as enabled or available in chrome://gpu output
-
Check for Chromium-based browsersIdentify any Chromium-based browsers installed (Microsoft Edge, Brave, Opera, etc.) and check their version numbers if they embed the Dawn componentAffected if A Chromium-based browser with Dawn version prior to the Chrome 126 fix is installed and WebGPU is accessible
-
Check Fedora system packagesOn Fedora systems, run 'rpm -q chromeos-common' or check package manager for dawn-related packages if manually installed outside the standard Chrome packageAffected if Running Fedora 39 or 40 with Dawn packages that have not been patched to the corrected version
You are affected if Google Chrome (or a Chromium-based browser embedding Dawn) version is below 126.0.6478.54 AND WebGPU functionality is enabled or accessible in the browser.
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 · scoped126.0.6478.54
Update Google Chrome to version 126.0.6478.54 or later to obtain the patched Dawn implementation.
Chrome 126.0.6478.54 or later
- Update Google Chrome to version 126.0.6478.54 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or download from the official Chrome download page
- For Fedora systems, run 'sudo dnf update google-chrome-stable' to receive the patched version once available in Fedora repositories, or wait for the automatic system update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5834 — 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-5834 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