CVE-2026-54545

@wakaru/cli arbitrary file write during bundle unpack

Workarounds

Do not run wakaru --unpack on untrusted or unknown bundles with affected versions.

If upgrading immediately is not possible, avoid using `--unpack on files that may be attacker-controlled.

@wakaru/cli is vulnerable to arbitrary file write when unpacking a crafted JavaScript bundle with --unpack.

Bundle-controlled module filenames were sanitized before writing extracted modules to the output directory. A crafted filename containing overlapping path traversal characters, such as ....//, could be transformed into ../ after sanitization. This allowed the final output path to escape the intended output directory.

An attacker who can cause a user to run wakaru --unpack on a malicious bundle may be able to write files outside the selected output directory. Depending on the target path and user environment, this may lead to code execution.

Affected versions: >=1.0.0 <1.4.0.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-54545 has a CVSS score of 7.1 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue has been patched in @wakaru/[email protected].

Users should upgrade to:

npm install @wakaru/cli@latest

or specifically:

npm install @wakaru/[email protected]

1. What is CVE-2026-54545? CVE-2026-54545 is a high-severity path traversal vulnerability in @wakaru/cli (npm), affecting versions >= 1.0.0, < 1.4.0. It is fixed in 1.4.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-54545? CVE-2026-54545 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of @wakaru/cli are affected by CVE-2026-54545? @wakaru/cli (npm) versions >= 1.0.0, < 1.4.0 is affected.
4. Is there a fix for CVE-2026-54545? Yes. CVE-2026-54545 is fixed in 1.4.0. Upgrade to this version or later.
5. Is CVE-2026-54545 exploitable, and should I be worried? Whether CVE-2026-54545 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54545 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54545? Upgrade @wakaru/cli to 1.4.0 or later.