Snyk CLI Insertion of Sensitive Information into Log File allowed in DEBUG or DEBUG/TRACE mode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

1.2 · 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 · score source

EPSS

• CVE-2025-6624: 0.18% estimated exploitation activity in the next 30 days; percentile 7.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 (SNYKREGISTRYUSERNAME and SNYKREGISTRYPASSWORD), 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…

Published by the source

26 Jun 2025, 06:31 UTC

Last modified by the source

28 Jul 2025, 20:42 UTC

Source last checked

26 Oct 2026, 12:37 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6hwc-9h8r-3vmf

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6hwc-9h8r-3vmf

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-6624

Advisory: Snyk CLI Insertion of Sensitive Information into Log File allowed in DEBUG or DEBUG/TRACE mode
IDs: CVE-2025-6624, GHSA-6hwc-9h8r-3vmf
Record: https://patchnext.com/advisories/cve-2025-6624 (revision 3, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: snyk 1.1297.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm snyk: affected < 1.1297.3; fixed in 1.1297.3
- Go github.com/snyk/go-application-framework: affected every version

## Suggested inspection (read-only)
- `npm ls snyk --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- Go github.com/snyk/go-application-framework: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on snyk, github.com/snyk/go-application-framework.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6hwc-9h8r-3vmf (OSV record GHSA-6hwc-9h8r-3vmf lists affected ranges: npm snyk >=0 =0)
- Verified: https://github.com/advisories/GHSA-6hwc-9h8r-3vmf (GitHub-reviewed advisory GHSA-6hwc-9h8r-3vmf lists affected ranges: npm snyk >=0 <1.1297.3)

Commands are suggestions: review each one before running it.