CVE-2026-134457 in Hysteria
Summary
by MITRE • 11/21/2026
Hysteria 2.5.0 before 2.8.2 contains a memory allocation vulnerability when sniffing is enabled, allowing authenticated users to trigger out-of-memory conditions. Attackers with a valid password can forward a crafted QUIC packet with a huge crypto length, causing the server to exhaust memory and crash.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in Hysteria versions prior to 2.8.2 represents a critical resource exhaustion flaw rooted in improper input validation during network traffic inspection. Specifically, when the sniffing feature is enabled, the application processes incoming QUIC packets with insufficient checks on their structural integrity and size constraints. This architectural oversight allows an authenticated attacker to exploit the memory allocation mechanisms by submitting crafted QUIC packets that contain excessively large crypto length fields. The server attempts to allocate memory corresponding to these inflated values without verifying whether such allocations are feasible within the system's available resources, leading directly to out-of-memory conditions.
From a technical perspective, this flaw aligns with CWE-789: Memory Allocation with Excessive Size, which describes scenarios where software allocates more memory than intended or possible due to flawed size calculations or missing bounds checks. The vulnerability is particularly severe because it requires authentication, meaning the attacker must possess valid credentials for the Hysteria service. However, once authenticated, the ability to trigger a denial of service via resource exhaustion significantly impacts system availability. This behavior maps directly to MITRE ATT&CK technique T1498: Network Denial of Service, specifically under the sub-technique of Resource Exhaustion Attacks, where adversaries aim to degrade or halt services by consuming critical resources such as memory or CPU cycles.
The operational impact of this vulnerability is primarily a denial of service against the Hysteria proxy server and potentially other services running on the same host if system-wide resource limits are breached. By forcing the application into an out-of-memory state, attackers can cause the process to crash or become unresponsive, disrupting legitimate traffic flow and requiring manual intervention or automatic restart mechanisms to restore functionality. In environments where high availability is critical, such as enterprise remote access solutions, this vulnerability poses a significant risk to business continuity.
Mitigation strategies should prioritize immediate patching to version 2.8.2 or later, which addresses the underlying memory allocation logic by implementing strict size limits and validation checks on incoming QUIC packet headers. In addition to updating software, administrators should enforce strong authentication policies using multi-factor authentication where possible to reduce the attack surface for credential-based exploitation. Network-level controls such as rate limiting and deep packet inspection can also help detect and block anomalous traffic patterns indicative of this exploit attempt before they reach the application layer. Regular security audits focusing on resource management in network-facing applications are recommended to prevent similar vulnerabilities from being introduced during future development cycles.