What is the CVSS score of CVE-2025-6624?

CVE-2025-6624 has a contested CVSS base score of 1.2 from a third party (e.g. CISA-ADP), while the vendor rates it Low. vuln.today uses the vendor rating as authoritative.

Which versions of Docker are affected by CVE-2025-6624?

CVE-2025-6624 presents moderate security risk, a log file exposure vulnerability rated CVSS 7.2.. A patch is available.

How to fix or mitigate CVE-2025-6624?

Within 7 days: Identify all affected systems and apply vendor patches promptly. Vendor patch is available.

Docker CVE-2025-6624

EUVD-2025-19191 LOW

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

2025-06-26 report@snyk.io

GHSA-6hwc-9h8r-3vmf

Information Disclosure Docker

Low

Disputed · 1.2 NVD

Severity by source

Sources disagree (Low–High)

NVD PRIMARY

1.2 LOW

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

SUSE

7.2 HIGH

AV:L/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorNVD

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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Local

Attack Complexity

High

Privileges Required

High

User Interaction

Scope

Lifecycle Timeline

Severity Changed

Apr 29, 2026 - 01:11 NVD

HIGH LOW

CVSS changed

Apr 29, 2026 - 01:11 NVD

7.2 (HIGH) 1.2 (LOW)

EUVD ID Assigned

Mar 15, 2026 - 23:54 euvd

EUVD-2025-19191

Analysis Generated

Mar 15, 2026 - 23:54 vuln.today

Patch released

Mar 15, 2026 - 23:54 nvd

Patch available

CVE Published

Jun 26, 2025 - 05:15 nvd

HIGH 7.2

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 npm packages depend on snyk (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.1297.3.

DescriptionCVE.org

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.