← Back
GHSA-fr4h-3cph-29xv
Path Traversal in pnpm (GHSA-fr4h-3cph-29xv)
Summary
path traversal in pnpm (GHSA-fr4h-3cph-29xv). Risk of unauthorized operations or information disclosure. Exploitable via ``node_modules``. Mitigation: upgrade to `11.7.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-fr4h-3cph-29xv** has been found in pnpm.
Attackers can target a specific entry point like ``node_modules`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pnpm to **11.7.0** or later.
If unsure, ask your IT team or search "pnpm GHSA-fr4h-3cph-29xv" on the vendor's site.
GHSA-fr4h-3cph-29xv (pnpm) — CWE-22 /
Attack surface: `node_modules` / `dep.name` / `dep.0.name` / `ERR_PNPM_INVALID_DEPENDENCY_NAME`
Patched: `11.7.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in pnpm. Attackers reach the vulnerable code path via ``node_modules`` without authentication.
📍 Affected scope
pnpm — . Attack surface: `node_modules` / `dep.name` / `dep.0.name` / `ERR_PNPM_INVALID_DEPENDENCY_NAME`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **11.7.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pnpm' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pnpm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pnpm` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pnpm to 11.7.0ステージング環境で 11.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
pnpm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.7.0"}]}]