Skip to content

← Public intelligence

npm package

@wakaru/cli

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1npmPublished

    @wakaru/cli arbitrary file write during bundle unpack

    CVE-2026-54545 · GHSA-7wpj-vvmv-pgm8

    Affected
    • npm @wakaru/cli >= 1.0.0, < 1.4.0
    Fixed in
    1.4.0· Vendor fix available
    Issue
    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/cli@1.4.0. Users should upgrade to: or specifically: 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.

    Recommended action: Upgrade to 1.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →