# CVE-2026-97359: HFS2 2.4.0 RCE via Multipart Upload Filename Template Injection

> Unauthenticated attackers can achieve remote code execution on HFS2 servers by injecting malicious template syntax into multipart upload filenames.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-2w8r-rhgc-4pch

## What is CVE-2026-97359?

CVE-2026-97359 is a critical code injection vulnerability in rejetto hfs2, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HFS2 version 2.4.0 and earlier contains a template injection vulnerability in the multipart upload handler that allows unauthenticated attackers to achieve remote code execution by embedding malicious template syntax in a filename. Attackers can craft a filename containing a closing template quoting sequence followed by an exec macro, which bypasses the authorization check in the dispatcher to execute arbitrary commands on the underlying host system.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2026-97359 being exploited?

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

Public exploit code:

- Rejetto HTTP File Server 2.4.x - Template Injection (nuclei): http/cves/2026/CVE-2026-97359.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97359 is a critical code injection vulnerability in rejetto hfs2, published on 24 Sep 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-97359 exists.

Affected product: rejetto hfs2. 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-97359/ (Markdown: https://insights.sbomify.com/CVE-2026-97359/index.md)
```

## Sources

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

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