# CVE-2026-101043: pnpm 11.0.0 before 11.11.0 Environment Variable Exfiltration via Proxy Settings

> Attackers can exfiltrate environment secrets by manipulating proxy settings in a project manifest, tricking pnpm into sending sensitive data to attacker-controlled hosts.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-49pq-2gf3-jw76, GHSA-vx52-2968-3vc6, MINI-m82x-vw9h-g422

## What is CVE-2026-101043?

CVE-2026-101043 is a high-severity vulnerability in pnpm, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

pnpm versions 11.0.0 before 11.11.0 and 10.7.0 before 10.34.5 expand ${VAR} environment-variable placeholders in the httpProxy, httpsProxy, and noProxy settings read from a project's pnpm-workspace.yaml. Because the manifest is repository-controlled and the proxy keys were omitted from the request-destination key set that otherwise suppresses placeholder expansion for untrusted manifests (as already done for registry, pnprServer, registries and namedRegistries), an attacker who controls a repository's pnpm-workspace.yaml can cause a victim who clones the repository and runs a pnpm command (e.g. pnpm install) to expand environment secrets such as NPM_TOKEN or GITHUB_TOKEN into a proxy hostname or userinfo and route install traffic — and the corresponding DNS lookups — through an attacker-controlled host. The exfiltration occurs during configuration loading, before any lifecycle script executes. Fixed in pnpm 11.11.0 and 10.34.5.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

4 open source packages ship an affected version, including pnpm.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pnpm` | npm | From 10.7.0 | 10.34.5 |
| `pnpm` | npm | From 10.7.0 | 10.34.5 |
| `pnpm` | npm | From 11.0.0 | 11.11.0 |
| `pnpm` | npm | From 11.0.0 | 11.11.0 |

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

Upgrade pnpm to a fixed version for your release line: 10.34.5 or 11.11.0.

## Is CVE-2026-101043 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101043 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-101043 is a high-severity vulnerability in pnpm, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101043 exists.

Affected packages and fixed versions:
- pnpm (npm): affected from 10.7.0; fixed in 10.34.5
- pnpm (npm): affected from 10.7.0; fixed in 10.34.5
- pnpm (npm): affected from 11.0.0; fixed in 11.11.0
- pnpm (npm): affected from 11.0.0; fixed in 11.11.0

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-101043/ (Markdown: https://insights.sbomify.com/CVE-2026-101043/index.md)
```

## Sources

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

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