Path Traversal in @wakaru/cli (CVE-2026-54545)
Summary
Path traversal in @wakaru/cli (CVE-2026-54545). Data can be tampered with by attackers. Mitigation: upgrade to 1.4.0 or later.
Original description
The description as published by the source.
wakaru is a JavaScript decompiler and unminifier toolkit. From 1.0.0 until 1.4.0, @wakaru/cli sanitizes bundle-controlled module filenames only once before writing extracted modules, so a crafted filename containing overlapping traversal sequences such as ....// collapses to ../ after sanitization and lets the final output path escape the selected output directory, allowing an attacker who can cause a user to run wakaru --unpack on a malicious bundle to write files outside that directory and, depending on the target path and environment, potentially achieve code execution. This issue is fixed in @wakaru/cli 1.4.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54545 has been found in @wakaru/cli.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @wakaru/cli to 1.4.0 or later.
If unsure, ask your IT team or search "@wakaru/cli CVE-2026-54545" on the vendor's site.
CVE-2026-54545 (@wakaru/cli) — CWE-22 / CVSS v3 7.1
Attack vector: local / unauthenticated
Patched: 1.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in @wakaru/cli.
Check the vendor advisory for the affected versions of @wakaru/cli.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 1.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@wakaru/cli' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@wakaru/cli' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@wakaru/cliを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @wakaru/cli to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com