CVE-2025-57783: Hiawatha Web server · HTTP Request Smuggling
Affects Hiawatha Web serverSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| HiawathaHiawatha Web server | Affected
| Fixed in– |
GitHubhsleisink/hiawathapkg:github/hsleisink/hiawathaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor Hiawatha project communications closely for official patches addressing CVE-2025-57783 and apply updates promptly once available. 2. Until a patch is released, implement strict input validation and HTTP header filtering at the network perimeter or reverse proxy level to detect and block malformed or ambiguous HTTP requests that could be used for request smuggling. 3. Deploy or tune Web Application Firewalls (WAFs) to recognize and mitigate HTTP request smuggling patterns, including anomalies in Content-Length and Transfer-Encoding headers. 4. Conduct thorough security testing, including fuzzing and penetration testing, focusing on HTTP request parsing behavior to identify potential exploitation paths. 5. Segment and isolate critical web server infrastructure to limit lateral movement in case of compromise. 6. Review and harden access control policies on the web server to minimize exposure of sensitive resources. 7. Educate security teams about HTTP request smuggling techniques and signs of exploitation to improve detection and response capabilities. 8. Consider temporary mitigation by disabling or restricting HTTP/1.1 pipelining or keep-alive connections if feasible, as these features can be exploited in request smuggling attacks.
Description
Improper header parsing may lead to request smuggling has been identified in Hiawatha webserver version 11.7 which allows an unauthenticated attacker to access restricted resources managed by Hiawatha webserver.