Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 7.5, published 26 June 2026.
- Which products and versions are affected?
- Apernet Hysteria < 2.9.2; github.com/apernet/hysteria (Go) < 2.9.2.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-26: Version 2.9.2 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Apernet Hysteria or github.com/apernet/hysteria (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the 'sniff' implementation of the Hysteria server. When protocol sniffing is enabled, the server attempts to identify the protocol of incoming connections. However, it does not enforce a maximum size limit for HTTP headers. An attacker can establish a connection and continuously stream large amounts of header data without the terminating CRLF sequence. This causes the server to buffer the data indefinitely until it exhausts available system memory (OOM), resulting in a Denial of Service. The issue is fixed in version 2.9.2.
Affected products
- apernet Hysteria < 2.9.2
Timeline
- 2026-05-23: disclosed
- 2026-06-26: advisory: GitHub Advisory published
- 2026-06-26: patched: Version 2.9.2 released