CyberSecBulletin
CVE-2025-6624NVD status: Analyzed

snyk: Insertion of Sensitive Information into Log File

CVE-2025-6624 is a high-severity insertion of sensitive information into log file vulnerability in snyk, with a CVSS 3.1 base score of 7.2 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, but only if a user takes part, for example by opening a link or file. The record lists version 1.1297.3 as the first without the flaw, so updating snyk to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update snyk to 1.1297.3 or a later version.
  2. Update Snyk Cli to 1.1297.3 or a later version.
  3. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
Snyksnykbefore 1.1297.31.1297.3
SnykSnyk Clibefore 1.1297.31.1297.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
HighAdministrator-level access is required first.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H. Scored by CNA (snyk.io).

Scoring systemScoreSeverityScored by
CVSS 4.01.2LowCNA (snyk.io)
CVSS 3.17.2HighCNA (snyk.io)

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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How developers prevent this class of flaw

  • Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Remove debug log files before deploying the application into production.
  • Protect log files against unauthorized read/write.

More Insertion of Sensitive Information into Log File vulnerabilities (CWE-532)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Other references

Other vulnerabilities in snyk

All snyk vulnerabilities

Recent Insertion of Sensitive Information into Log File vulnerabilities

Spotted an error? Tell us.