Executive brief
Snyk CLI, a widely-used security scanning tool, inadvertently logs sensitive credentials (container registry passwords, authentication tokens) to debug log files when running in DEBUG or DEBUG/TRACE mode. An attacker with local access to the machine running Snyk CLI could read these log files to obtain credentials for container registries and cloud services, potentially enabling unauthorized access to container repositories and Snyk accounts.
Technical details
The vulnerability is an Insertion of Sensitive Information into Log File (CWE-532) affecting Snyk CLI versions before 1.1297.3. When executing snyk container test/monitor, snyk auth, or snyk iac test commands with DEBUG or TRACE logging enabled, the tool fails to properly sanitize credentials before writing them to local debug logs. Affected credentials include container registry credentials (SNYK_REGISTRY_USERNAME, SNYK_REGISTRY_PASSWORD environment variables and --username/--password CLI flags), Snyk authentication tokens (in auth command with TRACE level), and Docker registry tokens (in IAC custom rules bundles). The attack requires local filesystem access to read the debug logs. The vulnerability was patched in version 1.1297.3 and corresponding fixes were applied to the go-application-framework dependency.
Affected products
- Snyk CLI before 1.1297.3
Timeline
- 2025-06-26: disclosed
- 2025-06-23: patched: Version 1.1297.3 released