We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
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.
Reserved 2025-06-25 | Published 2025-06-26 | Updated 2025-06-26 | Assigner snykInsertion of Sensitive Information into Log File
Snyk Research Team
security.snyk.io/vuln/SNYK-JS-SNYK-10497607
github.com/...ommit/38322f377da7e5f1391e1f641710be50989fa4df
github.com/snyk/cli/releases/tag/v1.1297.3
docs.snyk.io/snyk-cli/debugging-the-snyk-cli
github.com/...ommit/ca7ba7d72e68455afb466a7a47bb2c9aece86c18
Support options
