Path Traversal in banks (CVE-2026-71492)
Summary
Path traversal in banks (CVE-2026-71492). Risk of unauthorized operations or information disclosure. Exploitable via Prompt.name. Mitigation: upgrade to 2.4.5 or later.
Original description
The description as published by the source.
Banks generates meaningful LLM prompts using a simple template language. Prior to version 2.4.5, DirectoryPromptRegistry.set() in src/banks/registries/directory.py interpolates attacker-controlled Prompt.name and Prompt.version values into a Path without canonicalization or containment validation. Relative traversal such as ../victim/foo and an absolute Prompt.name can escape or discard the configured registry root, while overwrite=True permits replacement of existing target files. The poisoned name is persisted in index.json and reconstructed by _load(), allowing the out-of-root path to survive later registry loads. An application that forwards request data into these fields can therefore write Prompt.raw bytes to attacker-chosen paths writable by the application process. This issue is fixed in version 2.4.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-71492 has been found in banks.
Attackers can target a specific entry point like Prompt.name over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade banks to 2.4.5 or later.
If unsure, ask your IT team or search "banks CVE-2026-71492" on the vendor's site.
CVE-2026-71492 (banks) — CWE-22
Attack surface: Prompt.name / Path / pathlib / name
Patched: 2.4.5 — 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 banks. Attackers reach the vulnerable code path via Prompt.name.
Check the vendor advisory for the affected versions of banks. Attack surface: Prompt.name / Path / pathlib / name.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.4.5.
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 'banks' . 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 'banks' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
banksを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade banks to 2.4.5ステージング環境で 2.4.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com