Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.8amended

pnpm: Tarball hash of GitHub git dependencies is not stored in lockfile

CVE-2026-48995GHSA-hg3w-7f8c-63hp

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (pnpm 11.0.7, 10.33.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm pnpm

    Affected
    < 10.33.4>= 11.0.0, < 11.0.7
    Fixed in
    10.33.4, 11.0.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.8 · 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 · score source
EPSS
  • CVE-2026-48995: 0.17% estimated exploitation activity in the next 30 days; percentile 6.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 Given the following package.json: This produces a lockfile like so: 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-hg3w-7f8c-63hp

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-hg3w-7f8c-63hp

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-48995

Advisory: pnpm: Tarball hash of GitHub git dependencies is not stored in lockfile
IDs: CVE-2026-48995, GHSA-hg3w-7f8c-63hp
Record: https://patchnext.com/advisories/cve-2026-48995 (revision 3, source checked 26 Oct 2026, 12:56 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pnpm 11.0.7, 10.33.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm pnpm: affected < 10.33.4; >= 11.0.0, < 11.0.7; fixed in 10.33.4, 11.0.7

## Suggested inspection (read-only)
- `npm ls pnpm --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pnpm.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-hg3w-7f8c-63hp (OSV record GHSA-hg3w-7f8c-63hp lists affected ranges: npm pnpm >=0 =11.0.0 <11.0.7 (fixed))
- Verified: https://github.com/advisories/GHSA-hg3w-7f8c-63hp (GitHub-reviewed advisory GHSA-hg3w-7f8c-63hp lists affected ranges: npm pnpm >=0 =11.0.0 <11.0.7)

Commands are suggestions: review each one before running it.

Loading voting…