# CVE-2025-3911: Exposure in Docker Desktop logs of environment variables configured for running containers

> Attackers with log access can steal sensitive credentials from Docker Desktop logs, potentially leading to unauthorized system access.

- **Severity:** Medium 5.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2025
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-wpwc-6ghv-2w64

## What is CVE-2025-3911?

CVE-2025-3911 is a medium-severity vulnerability in Docker Desktop, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Recording 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-3911?


## How do I fix CVE-2025-3911?

No fix has been published for CVE-2025-3911 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-3911 being exploited?

There is no known exploitation of CVE-2025-3911 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3911 and fix it if it is affected.

What it is: CVE-2025-3911 is a medium-severity vulnerability in Docker Desktop, published on 29 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3911 in the wild and no public exploit code.

Affected product: Docker Desktop. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3911/ (Markdown: https://insights.sbomify.com/CVE-2025-3911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3911
- OSV: https://osv.dev/vulnerability/CVE-2025-3911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3911/
Summaries are generated and may contain mistakes; the official description above is the record.