CVE-2026-130756
Description
A flaw was found in pnpm standalone executables. This vulnerability can lead to arbitrary code execution through the distribution of malicious packages. The embedded runtime environment improperly trusts compromised intermediate Certificate Authority (CA) certificates when connecting to package registries. A network attacker possessing a compromised intermediate key can intercept Transport Layer Security (TLS) traffic and serve forged package metadata or malicious files to the client.
Statement
An improper certificate validation flaw exists in the standalone pnpm executable (@pnpm/exe) due to an embedded Node.js runtime that still trusts compromised eMudhra intermediate CA certificates during TLS connections. A network attacker positioned in a man-in-the-middle path with access to a compromised intermediate private key can intercept package registry fetches and serve forged package metadata or malicious tarballs, leading to arbitrary code execution.
Mitigation
Configure pnpm to route traffic through an internal trusted registry mirror or enforce a restricted custom CA trust store via the `cafile` configuration option instead of relying on the bundled default certificates. Restrict outbound network access from build and developer environments to known registry endpoints using egress firewall rules, and enforce lockfile integrity checks (`--frozen-lockfile`) during package installation.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 8.1 | N/A | 9.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Authentication
Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity
When a certificate is invalid or malicious, it might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client. The product might connect to a malicious host while believing it is a trusted host, or the product might be deceived into accepting spoofed data that appears to originate from a trusted host.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.