ChromeWeb browser · Google
CVE-2024-5830
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 · uneditedType Confusion in V8 in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to perform an out of bounds memory write 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 confidenceA type confusion vulnerability in Google Chrome's V8 JavaScript engine allows a remote attacker to perform out-of-bounds memory writes by tricking users into visiting a specially crafted HTML page. The vulnerability exists in Chrome versions prior to 126.0.6478.54.
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.
-
Verify Google Chrome is installedCheck for Chrome in the system browser list or look for the Chrome executable. On Windows, check Program Files/Google/Chrome/Application/chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.Affected if Google Chrome is installed on the system
-
Determine installed Chrome version via browser UIOpen Google Chrome, click the three-dot menu, go to Help > About Google Chrome. The version number is displayed on this page.Affected if The displayed version is prior to 126.0.6478.54 (for example, 125.0.6366.114 or earlier)
-
Determine installed Chrome version via command lineRun the command 'google-chrome --version' or 'chrome --version' in a terminal. Alternatively, on Windows, run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' in Command Prompt.Affected if The reported version is prior to 126.0.6478.54
-
Check Chrome version on Fedora systemsIf using Fedora 39 or 40 with a system-installed Chrome package, run 'rpm -qa | grep google-chrome' or 'dnf list installed google-chrome-stable' to see the installed package version.Affected if The installed package version on Fedora 39 or 40 is from before the security update was applied
A user is affected if Google Chrome is installed and the installed version number is less than 126.0.6478.54.
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 patch the V8 type confusion vulnerability.
Chrome 126.0.6478.54 or later
- Update Google Chrome to version 126.0.6478.54 or later
- On Fedora 39 or 40, run `sudo dnf update google-chrome-stable` or wait for the system package update to become available through standard system updates
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
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5830 — 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-5830 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