CVE-2026-134456 in Hysteriainfo

Summary

by MITRE • 11/21/2026

Hysteria 2.5.0 before 2.9.2 contains a denial of service vulnerability in the HTTP sniff implementation that fails to limit header size. Attackers can continuously send excessively large HTTP headers without terminating them, exhausting server memory and causing out-of-memory crashes.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/21/2026

The Hysteria proxy software, specifically versions prior to 2.9.2, contains a critical denial of service vulnerability within its HTTP sniffing implementation. This flaw stems from an absence of proper input validation regarding the size of incoming HTTP headers. In standard network protocols, header fields are expected to be bounded by reasonable limits to prevent resource exhaustion attacks. However, in this affected version, the application does not enforce any maximum length constraint on these headers. Consequently, a malicious actor can exploit this oversight by transmitting HTTP requests with excessively large or infinite header sizes that lack proper termination sequences. This behavior directly triggers an out-of-memory condition as the server attempts to allocate memory for processing the unbounded data structures associated with these malformed headers.

From a technical perspective, this vulnerability is classified under CWE-787: Out-of-bounds Write and CWE-400: Uncontrolled Resource Consumption. The core issue lies in the failure of the HTTP parser to implement boundary checks before allocating memory for header storage. When an attacker sends continuously large headers without termination, the server's memory allocation routine continues to expand its internal buffers indefinitely. This leads to rapid depletion of available system RAM. As the operating system struggles to manage these excessive allocations, it may invoke out-of-memory killers or simply cause the application process to crash due to insufficient resources. The lack of a defined limit for header size violates fundamental principles of secure coding practices which dictate that all external inputs must be validated against predefined constraints before processing.

The operational impact of this vulnerability is severe, resulting in a complete denial of service for users relying on Hysteria as a proxy or tunneling solution. Since the attack vector requires only network connectivity and does not necessitate authentication, it can be executed by any remote adversary with access to the target port. The consequence is an immediate disruption of services, leading to downtime and potential data loss if active connections are abruptly terminated during the crash event. Furthermore, repeated exploitation attempts could destabilize the underlying host system, affecting other processes running on the same machine. This type of attack aligns with MITRE ATT&CK technique T1498: Network Denial of Service, specifically under the sub-technique of resource exhaustion via application layer protocols.

To mitigate this vulnerability, organizations must upgrade Hysteria to version 2.9.2 or later where these bounds have been properly implemented. Until an update is applied, administrators should consider deploying web application firewalls or network intrusion prevention systems that can detect and block requests with abnormally large header sizes. Additionally, configuring reverse proxies such as Nginx or Apache in front of the Hysteria service can provide a layer of defense by enforcing strict limits on request headers before they reach the vulnerable application. It is also advisable to monitor server memory usage for anomalous spikes that may indicate ongoing exploitation attempts and to implement rate limiting policies to restrict the frequency of incoming connections from single sources.

Responsible

VulnCheck

Reservation

11/21/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!