# CVE-2025-1696: Exposure of Proxy Credentials in Docker Desktop Logs

> Attackers with log access can read proxy credentials from Docker Desktop logs, potentially enabling unauthorized access or further attacks.

- **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:** 6 Mar 2025
- **Updated:** 6 Mar 2025
- **Also known as:** GHSA-x75c-f5w5-hw79

## What is CVE-2025-1696?

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

### Official description

A vulnerability exists in Docker Desktop prior to version 4.39.0 that could lead to the unintentional disclosure of sensitive information via application logs. In affected versions, proxy configuration data—potentially including sensitive details—was written to log files in clear text whenever an HTTP GET request was made through a proxy. An attacker with read access to these logs could obtain the proxy information and leverage it for further attacks or unauthorized access. Starting with version 4.39.0, Docker Desktop no longer logs the proxy string, thereby mitigating this risk.

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

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


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

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

## Is CVE-2025-1696 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1696 is a medium-severity vulnerability in Docker Desktop, published on 6 Mar 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-1696 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-1696/ (Markdown: https://insights.sbomify.com/CVE-2025-1696/index.md)
```

## Sources

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

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