CVE-2026-48995: pnpm Tarball Hash Of GitHub Git Vulnerability

MODERATE
Advisory Identifier: GHSA-hg3w-7f8c-63hp
CWE-353
Published
Advisory Summary

CVE-2026-48995 is a MODERATE tarball hash of github git vulnerability (CWE-353: Missing Support for Integrity Check) affecting pnpm libraries in the npm ecosystem. The issue involves tarball hash of github git dependencies is not stored in lockfile. Remediation is available by upgrading affected packages to version 10.33.4, 11.0.7.

CVE-2026-48995 at a Glance

CVE Identifier CVE-2026-48995
GHSA Identifier GHSA-hg3w-7f8c-63hp
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-353: Missing Support for Integrity Check
Affected Product pnpm
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-48995

To remediate this vulnerability, upgrade all affected pnpm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

pnpm fixed: 10.33.4
npm install pnpm@10.33.4
pnpm fixed: 11.0.7
npm install pnpm@11.0.7
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls pnpm

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-48995, inspect your project dependencies using npm:

npm ls pnpm

Analyze the terminal output to locate any version of pnpm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 10.33.4), your application is affected.

Note: The npm ls pnpm command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-353: Missing Support for Integrity Check, where the product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum. In pnpm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A malicious `codeload.github.com` server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile. ### Details The lockfile does not store the hash of the dependencies from https://codeload.github.com This means that if this server was compromised or a person's machine configuration was compromised, pnpm would download and install these dependencies. ### PoC ```sh > pnpm -v 10.28.2 ``` Given the following package.json: ```json { "dependencies": { "add": "git://github.com/dsherret/npm-git-dep.git#b3eeb9b" } } ``` This produces a lockfile like so: ```yaml lockfileVersion: '9.0' settings: autoInstallPeers: true excludeLinksFromLockfile: false importers: .: dependencies: add: specifier: git://github.com/dsherret/npm-git-dep.git#b3eeb9b version: https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b packages: add@https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b: resolution: {tarball: https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b} version: 1.0.0 snapshots: add@https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b: {} ``` Notice that there is no hash. The `b3eeb9b` is not sufficient because I can configure my machine to resolve a compromised tarball from that url (I tested it out and pnpm just installs it). ### Impact Anyone relying on github git dependencies.

CVE-2026-48995 Affected pnpm Versions

2 component(s)
Fixed Versions:
10.33.411.0.7
Product / Package Ecosystem Affected Versions Fixed Version
pnpm
npm
< 10.33.4
10.33.4
pnpm
npm
≥ 11.0.0
< 11.0.7
11.0.7

References

Frequently Asked Questions

What is CVE-2026-48995?
CVE-2026-48995 is a security vulnerability in pnpm involving Tarball hash of GitHub git dependencies is not stored in lockfile under CWE-353: Missing Support for Integrity Check.
Which pnpm versions are affected?
Affected versions include releases prior to 10.33.4, 11.0.7 across affected packages: pnpm.
What version fixes CVE-2026-48995?
Upgrading to 10.33.4, 11.0.7 (or the latest patched release for your respective branch) resolves the vulnerability.
Is pnpm affected?
Yes, pnpm is affected in releases prior to 10.33.4, 11.0.7. Upgrade your dependency to 10.33.4, 11.0.7 or later.
What CWE is associated with CVE-2026-48995?
CVE-2026-48995 is classified under CWE-353: Missing Support for Integrity Check (The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.).
How can I check npm dependencies for CVE-2026-48995?
Run the dependency tree command: 'npm ls pnpm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hg3w-7f8c-63hp",
  "modified" : "2026-06-26T21:49:22Z",
  "published" : "2026-06-26T21:49:22Z",
  "aliases" : [ "CVE-2026-48995" ],
  "summary" : "pnpm: Tarball hash of GitHub git dependencies is not stored in lockfile",
  "details" : "### Summary\n\nA malicious `codeload.github.com` server can serve whatever tarball it wants and pnpm will install it regardless of the lockfile.\n\n### Details\n\nThe lockfile does not store the hash of the dependencies from https://codeload.github.com\n\nThis means that if this server was compromised or a person's machine configuration was compromised, pnpm would download and install these dependencies.\n\n### PoC\n\n```sh\n> pnpm -v     \n10.28.2\n```\n\nGiven the following package.json:\n\n```json\n{\n  \"dependencies\": {\n    \"add\": \"git://github.com/dsherret/npm-git-dep.git#b3eeb9b\"\n  }\n}\n```\n\nThis produces a lockfile like so:\n\n```yaml\nlockfileVersion: '9.0'\n\nsettings:\n  autoInstallPeers: true\n  excludeLinksFromLockfile: false\n\nimporters:\n\n  .:\n    dependencies:\n      add:\n        specifier: git://github.com/dsherret/npm-git-dep.git#b3eeb9b\n        version: https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b\n\npackages:\n\n  add@https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b:\n    resolution: {tarball: https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b}\n    version: 1.0.0\n\nsnapshots:\n\n  add@https://codeload.github.com/dsherret/npm-git-dep/tar.gz/b3eeb9b: {}\n```\n\nNotice that there is no hash. The `b3eeb9b` is not sufficient because I can configure my machine to resolve a compromised tarball from that url (I tested it out and pnpm just installs it).\n\n### Impact\n\nAnyone relying on github git dependencies.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "pnpm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "10.33.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "pnpm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "11.0.0"
      }, {
        "fixed" : "11.0.7"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/pnpm/pnpm/security/advisories/GHSA-hg3w-7f8c-63hp"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-48995"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/pnpm/pnpm"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-353" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-26T21:49:22Z",
    "nvd_published_at" : "2026-06-25T18:16:38Z"
  }
}