Skip to main content
Menu
CVEs

CVE

pnpm exe spoofed registry responses in bundled runtime

Standalone pnpm builds from @pnpm/exe embed a Node.js runtime that still trusts compromised eMudhra intermediate certificates. Fixed in 10.34.8 and 11.28.8.

CVE-2026-130756Published Updated Summary written by a model

9.3CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 10.34.8, 11.28.8
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 10.34.8, 11.28.8.

Summary

pnpm exe (@pnpm/exe) embeds an outdated Node.js runtime that still trusts compromised eMudhra intermediate CA certificates during registry TLS connections. A remote network attacker holding a recovered intermediate key can, without logging in or any user action, intercept standalone pnpm registry fetches and serve forged package metadata or tarballs.

Original description

pnpm exe before 10.34.8 embeds an outdated Node.js runtime that still trusts compromised eMudhra intermediate CA certificates during registry TLS connections. Network attackers holding a recovered intermediate key can intercept standalone pnpm registry fetches and serve forged package metadata or tarballs.

Who should check

Teams running standalone pnpm builds from @pnpm/exe, including the standalone install script and pnpm 12 users working in repositories pinned to 10.x or 11.x

Not fixed by: The 10.x line cannot get a patched runtime without moving to a newer Node.

“The @pnpm/exe standalone builds carry their own embedded Node.js”

github.com

cve.now Index

42Pcve.now Index 42 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach16/20@pnpm/exe: 8.7M downloads a week
  • Severity9.3/10CVSS 9.3
  • No patch0/5No signal

What would change the score

  • Would score about 87 if added to CISA KEV
  • Would score about 82 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Impact

  • Widely used

    @pnpm/exe has 8.7m weekly downloads.Source: npmjs.com

What to do

  • Upgrade to a fixed version: 10.34.8, 11.28.8.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130756 (pnpm exe before 10.34.8 Trusts Compromised eMudhra Intermediate Certificates), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130756 (entry last updated 2026-11-18):
Affected:
- npm package @pnpm/exe: fixed in 10.34.8
- npm package @pnpm/exe: from 11.0.0, fixed in 11.28.8
Fixed versions: 10.34.8, 11.28.8.
Conditions (all must be true for the bug to be hit):
- Standalone pnpm builds from @pnpm/exe embed their own Node.js runtime, which still trusts the compromised eMudhra intermediates (source: https://github.com/pnpm/pnpm/security/advisories/GHSA-w8f5-6m3h-r453)
- The registry fetch is made by a standalone pnpm build (source: https://github.com/pnpm/pnpm/security/advisories/GHSA-w8f5-6m3h-r453)
- Affected builds include pnpm 10.x and 11.x standalone builds with an older embedded Node (source: https://github.com/pnpm/pnpm/security/advisories/GHSA-w8f5-6m3h-r453)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130756 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130756 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pnpm/pnpm/security/advisories/GHSA-w8f5-6m3h-r453
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130756
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130756"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • fixed in 10.34.8

    Fixed in 10.34.8 (released Oct 22, 2026, 27 days before disclosure).

  • From 11.0.0 · fixed in 11.28.8

    Fixed in 11.28.8 (released Oct 22, 2026, 27 days before disclosure).

    The latest release, 12.21.0, is not affected.

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · pnpm/pnpm · Advisory GHSA-w8f5-6m3h-r453
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130756
RecordNVD · CVE-2026-130756

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130756

Is CVE-2026-130756 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The embedded Node.js runtime in standalone pnpm builds trusts compromised eMudhra intermediate certificates. A holder of a recovered intermediate key could serve forged registry responses to standalone pnpm, such as forged package metadata or tarballs.Source: github.com

Which versions are affected by CVE-2026-130756?

@pnpm/exe (npm): before 10.34.8. @pnpm/exe (npm): from 11.0.0 before 11.28.8.Source: cve.now feed data

Am I affected, and how do I check?

pnpm exe versions before 10.34.8 and versions 11.0.0 through 11.28.7 are in the affected ranges. The facts checked pnpm 10.33.4 and 10.34.7 standalone builds, which embedded Node 20.11.1. To check a setup, look at the pnpm version and confirm whether it is a standalone build from @pnpm/exe.Source: github.com

How do I fix CVE-2026-130756?

Upgrade to pnpm 10.34.8 or 11.28.8, the fixed versions for the 10.x and 11.x lines. No vendor patch identifiers are named in the facts.Source: github.com

More CVEs