# CVE-2026-130756: pnpm exe before 10.34.8 Trusts Compromised eMudhra Intermediate Certificates


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-952x-vv9w-c2gw, GHSA-w8f5-6m3h-r453

## What is CVE-2026-130756?

CVE-2026-130756 is a critical vulnerability in pnpm exe, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-130756?

2 open source packages ship an affected version, including %40pnpm/exe.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `%40pnpm/exe` | npm | `pkg:npm/%40pnpm/exe` | All versions | 10.34.8 |
| `%40pnpm/exe` | npm | `pkg:npm/%40pnpm/exe` | From 11.0.0 | 11.28.8 |

## How do I fix CVE-2026-130756?

Upgrade %40pnpm/exe to a fixed version for your release line: 11.28.8 or 10.34.8.

## Is CVE-2026-130756 being exploited?

There is no known exploitation of CVE-2026-130756 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130756 and fix it if it is affected.

What it is: CVE-2026-130756 is a critical vulnerability in pnpm exe, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130756 in the wild and no public exploit code.

Affected packages and fixed versions:
- %40pnpm/exe (npm): affected all versions; fixed in 10.34.8
- %40pnpm/exe (npm): affected from 11.0.0; fixed in 11.28.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130756/ (Markdown: https://insights.sbomify.com/CVE-2026-130756/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130756
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130756
- OSV: https://osv.dev/vulnerability/CVE-2026-130756

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130756/
Summaries are generated and may contain mistakes; the official description above is the record.
