Path Traversal in Pulpy (CVE-2026-44225)
Summary
Path traversal in Pulpy (CVE-2026-44225). Confidential information can be exposed externally. Mitigation: upgrade to 0.1.1 or later.
Original description
The description as published by the source.
Pulpy is a lightweight, cross-platform desktop application packager for web apps. Prior to 0.1.1, Pulpy injects a pulpy.fs JavaScript API into every packaged web application, giving it access to the host filesystem. A validateFsPath() function is supposed to sandbox this access, but its blocklist is incomplete. Any web app packaged with Pulpy can read and write arbitrary files in the user's home directory — including ~/.ssh/id_rsa, ~/.aws/credentials, and ~/Library/Keychains/. This vulnerability is fixed in 0.1.1.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44225 has been found in Pulpy.
Confidential information can be exposed externally. CVSS score: 9.3/10.
What to do: upgrade Pulpy to 0.1.1 or later.
If unsure, ask your IT team or search "Pulpy CVE-2026-44225" on the vendor's site.
CVE-2026-44225 (Pulpy) — CWE-22 / CVSS v3 9.3
Attack vector: remote (network-reachable) / unauthenticated
Patched: 0.1.1 — 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.
Path traversal (CWE-22) exists in Pulpy.
Check the vendor advisory for the affected versions of Pulpy.
Severity: Critical (CVSS 9.3/10). Confidential information can be exposed externally.
Update to 0.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Pulpy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Pulpy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Pulpyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Pulpy to 0.1.1ステージング環境で 0.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com