ChromeWeb browser · Google
CVE-2024-5839
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 Memory Allocator in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (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 · moderate confidenceA memory allocator implementation flaw in Google Chrome prior to version 126.0.6478.54 allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability stems from an inappropriate implementation in Chrome's memory allocator, which can lead to heap corruption that may be exploitable for arbitrary code execution.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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 Google Chrome version on Windows or MacOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if The displayed version is earlier than 126.0.6478.54
-
Check Google Chrome version on LinuxOpen a terminal and run: google-chrome --version or chromium --version depending on the installed package.Affected if The displayed version is earlier than 126.0.6478.54
-
Check Chrome version on Fedora via RPMOpen a terminal and run: rpm -q google-chrome or dnf list installed | grep chromeAffected if The installed version is earlier than 126.0.6478.54 or the package is not found (meaning Chrome may not be installed)
You are affected if Google Chrome (or Chromium on Fedora) is installed and its version number is lower 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. Organizations should deploy the update through standard patch management processes and verify compatibility with critical web applications.
Chrome 126.0.6478.54 or later (or latest stable)
- For Chrome Desktop users: Open Chrome, go to Settings > About Chrome, and the browser will automatically check for and install version 126.0.6478.54 or later
- Alternatively, download the latest Chrome stable build from the official Google Chrome website: https://www.google.com/chrome/
- For Fedora users: Run 'sudo dnf update chromium' or 'sudo dnf update google-chrome-stable' to install the patched version
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
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5839 — 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-5839 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