@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.
The issue has been patched in @wakaru/cli@1.4.0.
Users should upgrade to:
npm install @wakaru/cli@latest
or specifically:
npm install @wakaru/cli@1.4.0
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.
{
"nvd_published_at": null,
"severity": "HIGH",
"github_reviewed": true,
"github_reviewed_at": "2026-07-28T14:44:01Z",
"cwe_ids": [
"CWE-22"
]
}