GHSA-7WPJ-VVMV-PGM8

Vulnerability from github – Published: 2026-07-28 14:44 – Updated: 2026-07-28 14:44
VLAI
Summary
@wakaru/cli arbitrary file write during bundle unpack
Details

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:

npm install @wakaru/cli@latest

or specifically:

npm install @wakaru/cli@1.4.0

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.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "@wakaru/cli"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.0.0"
            },
            {
              "fixed": "1.4.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-54545"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-07-28T14:44:01Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\n`@wakaru/cli` is vulnerable to arbitrary file write when unpacking a crafted JavaScript bundle with `--unpack`.\n\nBundle-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.\n\nAn 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.\n\nAffected versions: `\u003e=1.0.0 \u003c1.4.0`.\n\n### Patches\n\nThe issue has been patched in `@wakaru/cli@1.4.0`.\n\nUsers should upgrade to:\n\n```sh\nnpm install @wakaru/cli@latest\n```\n\nor specifically:\n```\nnpm install @wakaru/cli@1.4.0\n```\n\n### Workarounds\n\nDo not run `wakaru --unpack` on untrusted or unknown bundles with affected versions.\n\nIf upgrading immediately is not possible, avoid using `--unpack on files that may be attacker-controlled.",
  "id": "GHSA-7wpj-vvmv-pgm8",
  "modified": "2026-07-28T14:44:02Z",
  "published": "2026-07-28T14:44:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/pionxzh/wakaru/security/advisories/GHSA-7wpj-vvmv-pgm8"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pionxzh/wakaru/commit/1d30383b20a6f768786b8ada2f1b0945de13c316"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/pionxzh/wakaru"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pionxzh/wakaru/releases/tag/v1.4.0"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "@wakaru/cli arbitrary file write during bundle unpack"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…