# CVE-2026-97362: HFS2 2.4.0 Unauthenticated Denial of Service via Hung Serving Thread

> Unauthenticated attackers can cause a persistent denial of service in HFS2 by triggering a hung serving thread, requiring manual restart.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 24 Sep 2026
- **Also known as:** GHSA-99rf-x5r6-q76q

## What is CVE-2026-97362?

CVE-2026-97362 is a high-severity denial of service 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 denial of service vulnerability that allows unauthenticated attackers to cause a complete and persistent loss of availability by sending a single crafted request. Attackers can trigger a hung serving thread that enters a busy loop, rendering the entire file server unresponsive to all clients without self-recovery until an operator manually restarts the service.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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


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

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

## Is CVE-2026-97362 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97362 is a high-severity denial of service 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-97362 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-97362/ (Markdown: https://insights.sbomify.com/CVE-2026-97362/index.md)
```

## Sources

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

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