CVE-2026-71492Public exploitNetwork attack vector

Arbitrary file write via prompt path traversal

Published Aug 20, 2026 · Updated Aug 20, 2026

Path traversal in DirectoryPromptRegistry.set() in Banks before 2.4.5 allows remote authenticated users to write files via crafted prompt fields. The method builds a filesystem path from untrusted Prompt.name and Prompt.version values, accepts dot segments and absolute names, writes Prompt.raw to the resolved path, and _load() later reconstructs the poisoned path from index.json. Exposure requires an application to pass user-controlled prompt metadata into the registry; overwrite=True also replaces existing writable files, but the documented impact is bounded to paths writable by the application process.

CVSS severity6.0
Medium
EPSS probability0.32%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in DirectoryPromptRegistry.set() in Banks before 2.4.5 allows remote authenticated users to write files via crafted prompt fields. The method builds a filesystem path from untrusted Prompt.name and Prompt.version values, accepts dot segments and absolute names, writes Prompt.raw to the resolved path, and _load() later reconstructs the poisoned path from index.json. Exposure requires an application to pass user-controlled prompt metadata into the registry; overwrite=True also replaces existing writable files, but the documented impact is bounded to paths writable by the application process.

The record

CVE
CVE-2026-71492
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
Massimiliano Pippi
Product
Banks
Classifications
CWE-22
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.4.5

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Massimiliano Pippi · Banksversion=< 2.4.5

Published CVSS scores

6.0GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo