# CVE-2026-62663: Banks: Arbitrary File Read via Path Traversal in Media Filters (image/audio/video/document)

> Attackers can read arbitrary files via path traversal in media filters, exposing sensitive data like credentials and keys in LLM prompts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-98rr-gvc9-3cjh

## What is CVE-2026-62663?

CVE-2026-62663 is a high-severity path traversal vulnerability in masci banks, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Banks generates meaningful LLM prompts using a simple template language. In versions prior to 2.4.4, all four media filters (image, audio, video, document) in banks accept untrusted user input as file paths via Path(value) and pass them directly to open(file_path, "rb") without any path sanitization, canonicalization, or directory restriction. An attacker who controls template variables passed to a banks Prompt can use path traversal (../) to read arbitrary files accessible to the Python process—including .env files, SSH keys, cloud credentials, source code, /etc/passwd, and /etc/shadow—with the content returned base64-encoded in the rendered prompt output, making exfiltration trivial. This is particularly dangerous for applications that use banks to process user-provided template variables before sending prompts to an LLM. This issue has been fixed in version 2.4.4.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-62663?


## How do I fix CVE-2026-62663?

No fix has been published for CVE-2026-62663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62663 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62663 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62663 and fix it if it is affected.

What it is: CVE-2026-62663 is a high-severity path traversal vulnerability in masci banks, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62663 exists.

Affected product: masci banks. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62663/ (Markdown: https://insights.sbomify.com/CVE-2026-62663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62663
- OSV: https://osv.dev/vulnerability/CVE-2026-62663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62663/
Summaries are generated and may contain mistakes; the official description above is the record.