CVE-2026-54545: @wakaru/cli arbitrary file write during bundle unpack
Impact @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.
Published Jul 28, 2026
Affected packages
@wakaru/cli
- Ecosystem
- npm
- Affected
- >= 1.0.0, < 1.4.0
- Fixed in
- 1.4.0
- Check
npm ls @wakaru/cli
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
@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.
Patches
The issue has been patched in @wakaru/[email protected].
Users should upgrade to:
npm install @wakaru/cli@latestor specifically:
npm install @wakaru/[email protected]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.
Credited to j4k0xb.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
