<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: snyk cli</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-6624: Versions of the package snyk before 1.1297.3 are vulnerable to Insertion of Sensitive Information into Log Fil</title><link>https://patchthecve.com/cve/CVE-2025-6624.html</link><guid>https://patchthecve.com/cve/CVE-2025-6624.html</guid><pubDate>Wed, 17 Jun 2026 10:02:16 +0000</pubDate><description>HIGH 7.2: 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/TRAC</description></item><item><title>CVE-2024-48964: The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted Gradle project</title><link>https://patchthecve.com/cve/CVE-2024-48964.html</link><guid>https://patchthecve.com/cve/CVE-2024-48964.html</guid><pubDate>Wed, 17 Jun 2026 07:59:08 +0000</pubDate><description>HIGH 7.5: The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted Gradle project. The vulnerability can be triggered if Snyk test is run inside the untrusted project due to the improper handling of the current working directory name. Snyk recommends only scanning truste</description></item><item><title>CVE-2024-48963: The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted PHP project</title><link>https://patchthecve.com/cve/CVE-2024-48963.html</link><guid>https://patchthecve.com/cve/CVE-2024-48963.html</guid><pubDate>Wed, 17 Jun 2026 07:59:07 +0000</pubDate><description>HIGH 7.5: The package Snyk CLI before 1.1294.0 is vulnerable to Code Injection when scanning an untrusted PHP project. The vulnerability can be triggered if Snyk test is run inside the untrusted project due to the improper handling of the current working directory name. Snyk recommends only scanning trusted p</description></item></channel></rss>