Is CVE-2025-6624 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-6624 being exploited in the wild.

How severe is CVE-2025-6624?

Low severity, with a CVSS score of 3.1, published 28 July 2025.

Which products and versions are affected?

github.com/snyk/go-application-framework (Go) SEMVER:introduced=0; snyk (npm) SEMVER:introduced=0,fixed=1.1297.3.

Is there a fix for CVE-2025-6624?

Yes. snyk (npm): upgrade to 1.1297.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-6624 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2025-6624?

Check whether you run github.com/snyk/go-application-framework (Go) or snyk (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-6624: Snyk CLI insertion of sensitive information in log files in DEBUG mode

CVE-2025-6624 · Severity: low · CVSS 3.1 · Published 2025-07-28

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.

Technologies: snyk (npm). Vendors: Go, npm.

Quick answers

Is CVE-2025-6624 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-6624 being exploited in the wild.
How severe is CVE-2025-6624?: Low severity, with a CVSS score of 3.1, published 28 July 2025.
Which products and versions are affected?: github.com/snyk/go-application-framework (Go) SEMVER:introduced=0; snyk (npm) SEMVER:introduced=0,fixed=1.1297.3.
Is there a fix for CVE-2025-6624?: Yes. snyk (npm): upgrade to 1.1297.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-6624 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2025-6624?: Check whether you run github.com/snyk/go-application-framework (Go) or snyk (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

snyk (npm): upgrade to 1.1297.3 or later
```
npm install snyk@1.1297.3
```

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

Identifiers

CVE-2025-6624
GHSA-6hwc-9h8r-3vmf
GO-2025-3789

Timeline

2025-06-26: disclosed
2025-06-23: patched: Version 1.1297.3 released

References

https://github.com/snyk/cli/commit/38322f377da7e5f1391e1f641710be50989fa4df

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.