CVE-2025-3911
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 · uneditedRecording of environment variables, configured for running containers, in Docker Desktop application logs could lead to unintentional disclosure of sensitive information such as api keys, passwords, etc. A malicious actor with read access to these logs could obtain sensitive credentials information and further use it to gain unauthorized access to other systems. Starting with version 4.41.0, Docker Desktop no longer logs environment variables set by the user.
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 prior to 4.41.0 recorded user-configured environment variables in application logs, which commonly contain sensitive credentials such as API keys, passwords, and tokens. Any user or process with read access to these logs could extract these credentials for unauthorized access to other systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Determine Docker Desktop versionRun `docker version` or open Docker Desktop and navigate to About Docker Desktop to view the version numberAffected if The installed version is earlier than 4.41.0
-
Locate Docker Desktop application logsOn Windows, check %LOCALAPPDATA%\Docker\log\ or C:\ProgramData\Docker\log\. On Mac, check ~/Library/Containers/com.docker.docker/Data/log/ or /var/log/docker.log. Consult Docker documentation for your OS version if these paths do not existAffected if Log files exist and are accessible to users or processes without elevated privileges
-
Search logs for environment variable contentUse a text search tool (such as grep, Select-String, or a text editor) to search log files for patterns resembling environment variable assignments (e.g., VAR_NAME=, export, or strings that look like API keys, tokens, or passwords)Affected if Log files contain lines with environment variable names or values, especially those resembling credentials
-
Identify sensitive credentials in logsManually review flagged log sections or search for common credential patterns: long alphanumeric strings after keywords like password=, token=, key=, secret=, api_key=, AWS_ACCESS_KEY=, or similarAffected if Logs contain actual credentials, API keys, tokens, or passwords in plain text
A user is affected if Docker Desktop version is below 4.41.0 and log files contain exposed environment variables with sensitive credentials accessible to unauthorized users or processes.
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 · scopedUpgrade Docker Desktop to version 4.41.0 or later, which stops logging environment variables. Audit logs for any prior exposure of credentials.
Docker Desktop 4.41.0 or later
- Back up any existing Docker Desktop configurations or data if needed
- Upgrade Docker Desktop to version 4.41.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3911 — 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-2025-3911 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