ChromeWeb browser · Google
CVE-2024-5840
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 · uneditedPolicy bypass in CORS in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to bypass discretionary access control 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 confidenceCORS policy bypass in Google Chrome prior to version 126.0.6478.54 allows a remote attacker to circumvent cross-origin restrictions via a crafted HTML page, potentially enabling unauthorized access to resources on other origins that should be protected by the Same-Origin Policy.
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.
-
Identify installed Google Chrome versionOpen Google Chrome, navigate to Help > About Google Chrome, or run 'google-chrome --version' in the terminalAffected if The displayed version is earlier than 126.0.6478.54
-
Check Chrome version on Windows via registryQuery the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome\DisplayVersion or HKEY_CURRENT_USER\Software\Google\Chrome\BLBeacon\versionAffected if The registry value shows a version lower than 126.0.6478.54
-
Check Chrome version on macOSRun '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in TerminalAffected if The version output is earlier than 126.0.6478.54
-
Verify Chrome package on Fedora LinuxRun 'rpm -q google-chrome' to check if installed, then 'rpm -q --qf '%{VERSION}-%{RELEASE}' google-chrome' to get the exact versionAffected if The package version is installed from Fedora 39 or 40 repos and is earlier than 126.0.6478.54
A user is affected if their installed Google Chrome version is lower than 126.0.6478.54, regardless of operating system.
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. In enterprise environments, deploy the browser update organization-wide and verify compliance.
Chrome 126.0.6478.54 (stable channel)
- Check current Chrome version by navigating to chrome://settings/help
- Update Chrome to version 126.0.6478.54 or later via the browser's built-in updater or your system's package manager
- For Fedora systems, run: sudo dnf update google-chrome-stable
- Restart Chrome after the update completes
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
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 locallyCheck whether your project pulls in CVE-2024-5840 — 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-5840 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