← Back
CVE-2026-53598
high
CVSS 7.5
Path Traversal in prompty (CVE-2026-53598)
Summary
path traversal in prompty (CVE-2026-53598). Confidential information can be exposed externally. Exploitable via ``prompty``. Mitigation: upgrade to `2.0.0b2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53598** has been found in prompty.
Attackers can target a specific entry point like ``prompty`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade prompty to **2.0.0b2** or later.
If unsure, ask your IT team or search "prompty CVE-2026-53598" on the vendor's site.
CVE-2026-53598 (prompty) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `prompty` / `Prompty.Core`
Patched: `2.0.0b2` — 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 prompty. Attackers reach the vulnerable code path via ``prompty`` without authentication.
📍 Affected scope
prompty — . Attack surface: `prompty` / `Prompty.Core`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.0.0b2**.
🛡️ 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 'prompty' .` 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 'prompty' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `prompty` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade prompty to 2.0.0b2ステージング環境で 2.0.0b2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
prompty
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0b2"}]}]
npm
@prompty/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]
rust
prompty
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]
nuget
Prompty.Core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.0-beta.2"}]}]