Docker DesktopApplication · Docker
CVE-2023-0626
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 · uneditedDocker Desktop before 4.12.0 is vulnerable to RCE via query parameters in message-box route. This issue affects Docker Desktop: before 4.12.0.
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 confidenceDocker Desktop versions prior to 4.12.0 contain a Remote Code Execution vulnerability in the message-box route that can be triggered through malicious query parameters. This allows unauthenticated attackers to potentially execute arbitrary code on affected systems.
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
Docker DesktopApplication
< 4.12.0CVSS 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.
-
Verify Docker Desktop is installedRun `docker desktop --version` on Windows or Mac, or check for Docker Desktop in the system (Windows: C:\Program Files\Docker\Docker\Docker Desktop.exe, Mac: /Applications/Docker.app)Affected if Docker Desktop is not found or the command is unavailable
-
Obtain the installed Docker Desktop version numberExecute `docker desktop --version` and record the full version string displayed (format typically shows as 4.x.x)Affected if Unable to retrieve a version number from the command output
-
Compare version against the affected rangeCompare the installed version to 4.12.0 - any version lower than 4.12.0 falls within the affected rangeAffected if Installed version is less than 4.12.0 (for example, 4.11.0, 4.10.0, or any earlier release)
The environment is affected if Docker Desktop is installed and the version number is below 4.12.0
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.12.0
Upgrade Docker Desktop to version 4.12.0 or later to remediate this critical RCE vulnerability.
Docker Desktop 4.12.0
- 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 the updates section
- If an update is available, download and install Docker Desktop 4.12.0 or later
- Restart Docker Desktop after the update completes
- Verify the version by running 'docker --version' or checking in the Docker Desktop UI
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Docker Desktop
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0626 — 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-2023-0626 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