Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-97362 Overview
CVE-2026-97362 is an unauthenticated denial of service vulnerability affecting HFS2 (HTTP File Server) version 2.4.0 and earlier. A single crafted request causes a serving thread to enter an infinite busy loop within the configuration parser. The hung thread exhausts the server's ability to respond, making the file server unresponsive to all clients. The condition persists until an operator manually restarts the service, with no self-recovery mechanism. The vulnerability is tracked under CWE-835 (Loop with Unreachable Exit Condition).
Critical Impact
An unauthenticated remote attacker can send one crafted request to permanently disable the HFS2 file server until manual intervention.
Affected Products
- HFS2 version 2.4.0
- HFS2 versions prior to 2.4.0
- HFS2 deployments exposing the HTTP file-serving interface to untrusted networks
Discovery Timeline
- 2026-09-24 - CVE-2026-97362 published to the National Vulnerability Database
- 2026-09-24 - Last updated in the NVD database
Technical Details for CVE-2026-97362
Vulnerability Analysis
HFS2 is a lightweight HTTP file server used to publish directories over the web. The vulnerability resides in the request-handling path that parses INI-style configuration data (getini). A specific input shape causes the parser to loop without ever reaching an exit condition. The worker thread assigned to the request never returns, consuming CPU and blocking subsequent requests queued against the same serving pipeline.
Because the loop is unbounded and the thread is pinned, no timeout, watchdog, or garbage-collection path recovers the resource. The server appears alive at the socket layer but stops answering HTTP requests. Operators must restart the HFS2 process to restore availability.
Root Cause
The root cause is a missing termination condition in the getini parsing routine when it encounters malformed or crafted input. The function iterates over input tokens without validating progress between iterations. See the GitHub advisory for HFS2 getini infinite loop DoS for technical details.
Attack Vector
Exploitation requires only network reach to the HFS2 HTTP interface. No authentication, user interaction, or prior access is needed. A single HTTP request containing the crafted payload is sufficient to hang a worker thread. Repeated requests can tie up additional threads and accelerate full service failure. Full technical details are available in the VulnCheck advisory for the HFS2 unauthenticated DoS.
Detection Methods for CVE-2026-97362
Indicators of Compromise
- A HFS2 process consuming sustained high CPU on one or more threads after receiving an HTTP request
- HFS2 TCP listener accepting connections but failing to return HTTP responses to legitimate clients
- Access logs that stop advancing while the process remains running
- Inbound requests targeting configuration or INI-handling endpoints from unexpected source addresses
Detection Strategies
- Monitor HFS2 worker threads for CPU time growth without corresponding request completion events
- Alert on HTTP response latency exceeding a defined threshold against the HFS2 service
- Correlate inbound HTTP requests with the subsequent cessation of successful responses to detect the trigger request
- Baseline normal HFS2 request-processing duration and alert on sustained outliers
Monitoring Recommendations
- Enable process-level telemetry to capture per-thread CPU utilization for the HFS2 binary
- Collect HTTP access and error logs centrally for correlation with network flow data
- Instrument synthetic health checks that validate end-to-end HTTP responses, not just port availability
- Capture packet metadata for requests immediately preceding service unresponsiveness to support root-cause analysis
How to Mitigate CVE-2026-97362
Immediate Actions Required
- Restrict network access to the HFS2 HTTP interface to trusted source addresses using firewall or ACL controls
- Remove HFS2 instances from direct internet exposure where possible
- Deploy a reverse proxy with request validation and rate limiting in front of HFS2
- Monitor for sudden loss of HTTP responsiveness and automate process restart as a stopgap
Patch Information
At the time of publication, no vendor patch is referenced in the NVD entry for CVE-2026-97362. Review the GitHub advisory for HFS2 getini infinite loop DoS and the VulnCheck advisory for updates on fixed versions and upgrade guidance.
Workarounds
- Place HFS2 behind a reverse proxy that enforces request size limits and strict input validation
- Use network segmentation to limit HFS2 reachability to known administrative hosts
- Configure an external process supervisor to detect unresponsiveness and restart HFS2 automatically
- Where feasible, migrate workloads to a maintained HTTP file-server implementation
# Example: restrict HFS2 (default TCP/80 or configured port) to trusted sources using iptables
iptables -A INPUT -p tcp --dport 80 -s 10.0.0.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j DROP
# Example: external watchdog using systemd to restart HFS2 on unresponsiveness
# /etc/systemd/system/hfs2.service
# [Service]
# ExecStart=/opt/hfs2/hfs2
# Restart=always
# WatchdogSec=30s
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

