Webpro-nl Knip Workspace IssueFixer.ts writeFile path traversal
Knip versions up to 6.39.0 are affected when a user runs knip --fix on an attacker-crafted repository. The checked facts list no vendor rating and no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Knip versions up to 6.39.0 are affected Victim runs knip --fix on an attacker-crafted repository
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 22/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Knip, a JavaScript/TypeScript project analysis tool by Webpro-nl, is affected through its workspace handling code, where a flaw in how file paths are processed can let an attacker write files to locations outside the intended directory. This could allow an attacker to overwrite or create arbitrary files on a system running the affected tool.
Read the original description
A security vulnerability has been detected in Webpro-nl Knip up to 6.44.0. The impacted element is the function writeFile of the file packages/knip/src/IssueFixer.ts of the component Workspace Handler. Such manipulation of the argument workspaces leads to path traversal. The attack can be executed remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
What to do
Check whether your setup matches what the bug needs.
Knip versions up to 6.39.0 are affected Victim runs knip --fix on an attacker-crafted repositoryWorkaround: Until a fix is available, avoid running knip --fix on repositories you did not create or do not trust. Running knip without --fix limits the affected feature to reporting only.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Webpro-nl Knip
6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 6.11, 6.12, 6.13, 6.14, 6.15, 6.16, 6.17, 6.18, 6.19, 6.20, 6.21, 6.22, 6.23, 6.24, 6.25, 6.26, 6.27, 6.28, 6.29, and 15 more
Evidence 5
- Advisory
- Advisory
- Advisory
- Advisory
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120325
What does this mean?
A path traversal flaw in Knip's IssueFixer.ts writeFile lets a crafted repository make knip --fix delete and overwrite files outside that repository on the victim's machine.Source: github.com
Am I affected, and how do I check?
Knip versions up to and including 6.39.0 are affected, and 6.39.0 was verified. To check an installed copy, run knip --version and compare the result with 6.39.0. The risk applies when knip --fix is run on a repository from an untrusted source.Source: github.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given. Check the Knip project's advisory or releases for a version newer than 6.39.0.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
Until a fix is available, avoid running knip --fix on repositories you did not create or do not trust. Running knip without --fix limits the affected feature to reporting only.Source: github.com