@wakaru/cli
Affected
- introduced
1.0.0, fixed1.4.0(semver)
Fixed versions
1.4.0
Fix
- Fixed version
1.4.0npm install @wakaru/[email protected]
Advisory
Also known as: 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. 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@latest
or 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.
High Basis: The source's own band: HIGH
1.0.0, fixed 1.4.0 (semver)1.4.0
1.4.0npm install @wakaru/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0