DesktopApplication · Docker
CVE-2024-8696
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 · uneditedA remote code execution (RCE) vulnerability via crafted extension publisher-url/additional-urls could be abused by a malicious extension in Docker Desktop before 4.34.2.
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 confidenceDocker Desktop versions before 4.34.2 contain an RCE vulnerability where a malicious extension can execute arbitrary code via crafted extension publisher-url or additional-urls parameters. The vulnerability is exploitable without additional privileges once a malicious extension is installed, allowing complete compromise of the host system.
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
DesktopApplication
< 4.34.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Docker Desktop versionOpen Docker Desktop and go to About Docker Desktop, or run 'docker --version' in the terminal to see the installed versionAffected if The installed version is earlier than 4.34.2 (e.g., 4.34.1, 4.34.0, 4.33.x, etc.)
-
List installed extensionsOpen Docker Desktop, navigate to the Extensions tab, or run 'docker extension ls' in the terminal to see all installed extensionsAffected if Any extension is installed from an untrusted or unknown source
-
Review extension sourcesFor each installed extension, inspect the extension details to identify the publisher-url and any additional-urls configuredAffected if Any extension has a publisher-url or additional-urls pointing to an untrusted or suspicious source
You are affected if Docker Desktop version is below 4.34.2 AND you have any extensions installed from untrusted sources.
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 · scoped4.34.2
Upgrade Docker Desktop to version 4.34.2 or later to remediate this vulnerability. Review installed extensions and remove any untrusted or suspicious extensions.
4.34.2
- Open Docker Desktop
- Click on the Docker Desktop icon in the system tray (Windows) or menu bar (Mac)
- Select 'Check for updates' or navigate to Settings > General
- If an update is available, click 'Update Now' and follow the prompts to download and install version 4.34.2 or later
- Restart Docker Desktop after the update completes
- Verify the update by checking Help > About Docker Desktop to confirm version 4.34.2 or higher is installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Desktop
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8696 — 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-8696 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