# CVE-2025-6624: Snyk CLI Insertion of Sensitive Information into Log File allowed in DEBUG or DEBUG/TRACE mode

> Attackers with local access can read sensitive container registry and authentication credentials from Snyk CLI debug logs when debug or trace modes are enabled.

- **Severity:** Low 2.4 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:N/VA:N/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Jun 2025
- **Updated:** 26 Jun 2025
- **Also known as:** GHSA-6hwc-9h8r-3vmf, GO-2025-3789

## What is CVE-2025-6624?

CVE-2025-6624 is a low-severity vulnerability in snyk, published on 26 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

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

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

5 open source packages ship an affected version, including github.com/snyk/go-application-framework and snyk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/snyk/go-application-framework` | Go | All versions | None |
| `github.com/snyk/go-application-framework` | Go | All versions | None |
| `github.com/snyk/go-application-framework` | Go | All versions | None |
| `snyk` | npm | All versions | 1.1297.3 |
| `snyk` | npm | All versions | 1.1297.3 |

Products: Snyk Snyk Cli.

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

Upgrade to a fixed version.

## Is CVE-2025-6624 being exploited?

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

## Other vulnerabilities in snyk

- [CVE-2024-48963](https://insights.sbomify.com/CVE-2024-48963/): OS Command Injection in Snyk php plugin (high 7.5)
- [CVE-2024-48964](https://insights.sbomify.com/CVE-2024-48964/): OS Command Injection in Snyk gradle plugin (high 7.5)
- [CVE-2022-24441](https://insights.sbomify.com/CVE-2022-24441/): Code Injection (medium 5.8)
- [CVE-2022-22984](https://insights.sbomify.com/CVE-2022-22984/): Command Injection (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6624 is a low-severity vulnerability in snyk, published on 26 Jun 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-6624 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/snyk/go-application-framework (Go): affected all versions; no fix listed
- github.com/snyk/go-application-framework (Go): affected all versions; no fix listed
- github.com/snyk/go-application-framework (Go): affected all versions; no fix listed
- snyk (npm): affected all versions; fixed in 1.1297.3
- snyk (npm): affected all versions; fixed in 1.1297.3

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-6624/ (Markdown: https://insights.sbomify.com/CVE-2025-6624/index.md)
```

## Sources

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

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