What is the severity of CVE-2025-3911?

CVE-2025-3911 is considered a medium severity vulnerability due to the potential exposure of sensitive information in Docker Desktop application logs.

How do I fix CVE-2025-3911?

To mitigate CVE-2025-3911, ensure that log access is restricted and avoid logging sensitive environment variables in Docker Desktop.

What types of sensitive information could be exposed by CVE-2025-3911?

CVE-2025-3911 could lead to the exposure of sensitive information such as API keys, passwords, and other confidential environment variables.

Who is affected by CVE-2025-3911?

CVE-2025-3911 affects users of Docker Desktop version 4.41.0 and later configurations.

Can CVE-2025-3911 be exploited remotely?

CVE-2025-3911 requires a malicious actor to have read access to the logs, meaning a remote exploitation is unlikely without prior access.

Vulnerability/
CVE-2025-3911

medium

5.2

CWE

532

EPSS

0.017%

29/4/2025

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

First published: Tue Apr 29 2025(Updated: )

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.

Credit: security@docker.com

Affected Software	Affected Version	How to fix
Docker Desktop	>=4.41.0

Never miss a vulnerability like this again

Reference Links

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

Frequently Asked Questions

What is the severity of CVE-2025-3911?
CVE-2025-3911 is considered a medium severity vulnerability due to the potential exposure of sensitive information in Docker Desktop application logs.
How do I fix CVE-2025-3911?
To mitigate CVE-2025-3911, ensure that log access is restricted and avoid logging sensitive environment variables in Docker Desktop.
What types of sensitive information could be exposed by CVE-2025-3911?
CVE-2025-3911 could lead to the exposure of sensitive information such as API keys, passwords, and other confidential environment variables.
Who is affected by CVE-2025-3911?
CVE-2025-3911 affects users of Docker Desktop version 4.41.0 and later configurations.
Can CVE-2025-3911 be exploited remotely?
CVE-2025-3911 requires a malicious actor to have read access to the logs, meaning a remote exploitation is unlikely without prior access.

collector/mitre-cve
source/MITRE
agent/references
agent/weakness
agent/title
agent/type
agent/description
agent/first-publish-date
agent/guess-ai
agent/software-canonical-lookup
agent/softwarecombine
collector/nvd-api
source/NVD
agent/author
agent/severity
agent/last-modified-date
agent/event
collector/epss-latest
source/FIRST
agent/source
agent/tags
agent/epss
vendor/docker
canonical/docker desktop

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.