Skip to content

onnxruntime-node: bump adm-zip to >=0.6.0 to resolve GHSA-xcpc-8h2w-3j85 #30125

Closed

Description

Problem

Current onnxruntime-node releases, including 1.27.0 and the latest 1.29.0-dev builds, declare adm-zip: ^0.5.16. All adm-zip versions below 0.6.0 are affected by GHSA-xcpc-8h2w-3j85 / CVE-2026-39244 (crafted ZIP metadata can trigger an approximately 4 GB allocation and process OOM).

Because ^0.5.16 cannot resolve to 0.6.0, downstream libraries cannot remediate this by widening their own direct adm-zip range: npm installs a nested vulnerable adm-zip@0.5.x under onnxruntime-node. Library-level overrides also do not propagate to consumers.

Reproduction

npm init -y
npm install onnxruntime-node@1.27.0 adm-zip@^0.6.0
npm ls adm-zip
npm audit

The tree contains both top-level adm-zip@0.6.0 and nested onnxruntime-node/node_modules/adm-zip@0.5.x; npm reports the high-severity advisory through onnxruntime-node.

Requested change

Please update the onnxruntime-node dependency to adm-zip >=0.6.0 (ideally ^0.6.0) and publish a patched stable release. adm-zip 0.6.0 is the first patched version. Its documented extraction behavior changes should be checked against the package-install extraction path.

This currently forces downstreams that need Intel macOS support to choose between an older ONNX Runtime release without the vulnerable dependency or carrying a native-package fork/consumer override.

Activity

  1. added
    platform:webissues related to ONNX Runtime web; typically submitted using template
    on Jul 28, 2026
  2. Nash6643 commented on Aug 5, 2026

    @Nash6643

    Verified on main branch inside js/node/package.json — adm-zip is already updated to ^0.6.0. Looks like this has been resolved

  3. microsoft-github-policy-service commented on Sep 5, 2026

    @microsoft-github-policy-service
    Contributor

    Applying stale label due to no activity in 30 days. Please react to the issue by assigning it or labeling it as 'contributions welcome', 'documentation', 'feature request', 'regression', or 'no stale'.

  4. microsoft-github-policy-service commented on Oct 6, 2026

    @microsoft-github-policy-service
    Contributor

    Applying stale label due to no activity in 30 days. Please react to the issue by assigning it or labeling it as 'contributions welcome', 'documentation', 'feature request', 'regression', or 'no stale'.

  5. microsoft-github-policy-service commented on Oct 6, 2026

    @microsoft-github-policy-service
    Contributor

    Closing issue due to no activity in 30 days

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    platform:webissues related to ONNX Runtime web; typically submitted using templatestaleissues that have not been addressed in a while; categorized by a bot

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions