ChromeWeb browser · Google

CVE-2024-5843

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-11

Fix available

A fix is available. Upgrade to 126.0.6478.54 or later.

See remediation →

72/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Inappropriate implementation in Downloads in Google Chrome prior to 126.0.6478.54 allowed a remote attacker to obfuscate security UI via a malicious file. (Chromium security severity: Medium)

Technical summary

dbcve analysis · high confidence

A vulnerability in Google Chrome's Downloads component prior to version 126.0.6478.54 allows a remote attacker to obfuscate security user interface elements using a malicious file. This UI obfuscation could trick users into making unsafe decisions about downloaded files.

MitigationUpdate Google Chrome to version 126.0.6478.54 or later. For enterprise environments, deploy the update via centralized patch management and verify all installations are patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 126.0.6478.54

FedoraOperating system

Affected:= 39= 40

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Chrome version via browser UI

Open a new tab and navigate to chrome://version. Locate the 'Chrome' row showing the full version number (e.g., 126.0.6478.54).

Affected if The version displayed is less than 126.0.6478.54 (e.g., 126.0.6478.53 or earlier).
Check Chrome version via command line

Open a terminal and run: google-chrome --version or chromium-browser --version. On Windows, run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version

Affected if The reported version is less than 126.0.6478.54.
Check Chrome package version on Fedora

Run: dnf list installed google-chrome (or rpm -qi google-chrome) to view the installed package version and release details.

Affected if The installed package version is earlier than 126.0.6478.54.
Verify the Downloads component is in use

This vulnerability affects the Downloads component. Open the Downloads page (chrome://downloads) or download any file to confirm the component is active.

Affected if The Downloads component is present and usable in the browser (the flaw applies to any use of this component in vulnerable versions).

You are affected if Google Chrome (or Chromium-based browser) version is earlier than 126.0.6478.54 and the Downloads component is accessible.

Generated from the published advisory. Verify against your own configuration.

Remediation

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. For enterprise environments, deploy the update via centralized patch management and verify all installations are patched.

Recommended fix High confidence

Chrome 126.0.6478.54 or later (Fedora packages should be updated to the version containing the CVE-2024-5843 fix)

For Chrome Desktop: Update Google Chrome to version 126.0.6478.54 or later by navigating to chrome://settings/help and clicking 'Update Google Chrome', or download the latest version from google.com/chrome
For Fedora systems: Run 'sudo dnf update google-chrome-*' to apply the security update containing the CVE fix
Restart the browser after updating to ensure the fix is fully applied

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

Fix this in Chrome Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,040

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

chromereleases.googleblog.comThird Party Advisory
lists.fedoraproject.orgThird Party Advisory
lists.fedoraproject.orgThird Party Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-5843 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-5843?

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.

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

At a glance

A fix existsUpgrade to 126.0.6478.54 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Chrome

Remediation

Need this fixed?

Fix this in Chrome 6 hrs · Low

Typical engagement from $1,040

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-5843 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References