high CVSS 7.2

CVE-2025-6624·Docker vulnerability

Versions of the package snyk before 1.1297.3 are vulnerable to Insertion of Sensitive Information into Log File through local Snyk CLI debug logs. Container Registry credentials provided via environment variables or command line arguments can be exposed when executing Snyk CLI in DEBUG or DEBUG/TRACE mode. The issue affects the following Snyk commands: 1. When snyk container test or snyk container monitor commands are run against a container registry, with debug mode enabled, the container registry credentials may be written into the local Snyk CLI debug log. This only happens with credentials specified in environment variables (SNYK_REGISTRY_USERNAME and SNYK_REGISTRY_PASSWORD), or in the CLI (--password/-p and --username/-u). 2. When snyk auth command is executed with debug mode enabled AND the log level is set to TRACE, the Snyk access / refresh credential tokens used to connect the CLI to Snyk may be written into the local CLI debug logs. 3. When snyk iac test is executed with a Remote IAC Custom rules bundle, debug mode enabled, AND the log level is set to TRACE, the docker registry token may be written into the local CLI debug logs.

Severity
high
Software
Docker
Fixed in
1.1297.3
Published
2025-06-26

Affected versions

Until: 1.1297.3

Fixed in: 1.1297.3

How to fix this CVE

Update Snyk CLI to version 1.1297.3 or later to prevent credential leakage in debug logs. This vulnerability allows container registry credentials, authentication tokens, and Docker registry access tokens to be written to local debug log files when debug or trace logging modes are enabled. Immediate patching is recommended for all Docker users who run Snyk CLI commands with debugging enabled.

sudo dnf upgrade docker-ce

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check Docker version with 'docker --version' and verify it includes Snyk CLI or run 'snyk --version' to check the CLI version directly
  2. Step 2: Search for debug log files in your home directory and temporary paths with 'find ~/.snyk* ~/.config/snyk* /tmp -name '*debug*' -o -name '*.log' 2>/dev/null'
  3. Step 3: Grep for exposed credentials in logs with 'grep -r "SNYK_REGISTRY_USERNAME\|SNYK_REGISTRY_PASSWORD\|Authorization\|Bearer" ~/.snyk* ~/.config/snyk* /tmp 2>/dev/null | head -20'
  4. Step 4: After upgrading, re-run 'snyk --version' and confirm the version is 1.1297.3 or higher, then delete old debug logs with 'rm -rf ~/.snyk* ~/.config/snyk*/*debug* /tmp/*snyk*.log'

FAQ

What is CVE-2025-6624?

CVE-2025-6624 is a credential exposure vulnerability in Snyk CLI where sensitive information such as container registry credentials, authentication tokens, and API keys are inadvertently written to local debug log files when debug or trace logging levels are enabled.

Is CVE-2025-6624 being actively exploited?

No, CVE-2025-6624 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the local nature of the vulnerability means attackers with file system access could retrieve exposed credentials.

What versions of Docker are affected by CVE-2025-6624?

All versions of Snyk CLI prior to 1.1297.3 are affected. The vulnerability impacts the snyk container test, snyk container monitor, snyk auth, and snyk iac test commands when executed with debug or trace logging enabled.

How do I check if my server is vulnerable to CVE-2025-6624?

Run 'snyk --version' to check your installed version. If the version is below 1.1297.3, your system is vulnerable. Additionally, check for debug logs in '~/.snyk' and '~/.config/snyk' directories that may contain exposed credentials.

Does Defensia detect CVE-2025-6624?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Snyk CLI or Docker is installed on a monitored server, CVE-2025-6624 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-33587CVSS 10Lack of user input sanitisation in Open Notebook v1.8.3 allows the application user to execute Python code (and subsequently OS commands) on the docker container via Server-Side Template Injection (SSTI) for user-created transformations.
CVE-2026-53576CVSS 10Kestra is an open-source, event-driven orchestration platform. Prior to 1.0.45 and 1.3.21, the authentication filter for the REST API (@Filter("/api/v1/**")) treats any request whose path ends in /configs as the public instance-config endpoint and forwards it without a credential check. kestra addresses its resources by URL path segments that the caller chooses (/api/v1/{tenant}/flows/{namespace}, /api/v1/{tenant}/executions/{namespace}/{id}, /api/v1/{tenant}/namespaces/{namespace}/kv/{key}). An anonymous caller picks the literal configs as the final segment, and the request bypasses Basic-Auth entirely. Because the bypass reaches the flow-create and execution-trigger routes, an unauthenticated caller creates a flow containing a Shell or Process task and runs it. The task executes as root inside the kestra container. The official docker-compose.yml mounts /var/run/docker.sock, so root in the container reaches the host Docker daemon. This vulnerability is fixed in 1.0.45 and 1.3.21.
CVE-2026-40281CVSS 10Gotenberg is a Docker-powered stateless API for PDF files. In versions 8.30.1 and earlier, the metadata write endpoint validates metadata keys for control characters but leaves metadata values unsanitized. A newline character in a metadata value splits the ExifTool stdin line into two separate arguments, allowing injection of arbitrary ExifTool pseudo-tags such as -FileName, -Directory, -SymLink, and -HardLink. This is a bypass of the incomplete key-sanitization fix introduced in v8.30.1. An unauthenticated attacker can rename or move any PDF being processed to an arbitrary path in the container filesystem, overwrite arbitrary files, or create symlinks and hard links at arbitrary paths.
CVE-2026-44329CVSS 10free5GC is an open-source implementation of the 5G core network. Prior to 4.2.2, free5GC's SMF mounts the UPI management route group without OAuth2/bearer-token authorization middleware. A network attacker who can reach SMF on the SBI can hit UPI endpoints with no Authorization header at all, and the requests reach the SMF business handlers. In the running Docker lab this was directly demonstrated for read (GET /upi/v1/upNodesLinks), write (POST /upi/v1/upNodesLinks with attacker-controlled UP-node and link payload), and delete (DELETE /upi/v1/upNodesLinks/{nodeID}) operations. This vulnerability is fixed in 4.2.2.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-6624. Free for 1 server.

Get started free