Skip to main content
Menu
CVEs

HyNetworks Hysteria remote memory exhaustion crash in QUIC sniffing

Only affects Hysteria servers from 2.5.0 through 2.8.1 that have sniffing enabled. Fixed in 2.8.2.

CVE-2026-134457Published November 21, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.8.2
Who is exposed
Specific setups only

Summary

Written by a model

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.

Who should check

Teams running Hysteria 2.5.0 through 2.8.1 servers with sniffing enabled, including anyone using the Go module github.com/apernet/hysteria/core/v2.

“Affecting hysteria >= 2.5.0, < 2.8.2”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    Hysteria 2.5.0 through 2.8.1 (fixed in 2.8.2) Server has sniffing enabled
  2. Upgrade to a fixed version: 2.8.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134457 (Hysteria 2.5.0 before 2.8.2 QUIC Packet OOM via Sniff Crypto Length), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134457 (entry last updated 2026-11-21):
Affected:
- Go package github.com/apernet/hysteria/core/v2: from 2.5.0, fixed in 2.8.2
Fixed versions: 2.8.2.
Conditions (all must be true for the bug to be hit):
- Hysteria 2.5.0 through 2.8.1 (fixed in 2.8.2) (source: https://www.vulncheck.com/advisories/hysteria-2.5.0-before-2.8.2-quic-packet-oom-via-sniff-crypto-length)
- Server has sniffing enabled (source: https://github.com/HyNetworks/hysteria/security/advisories/GHSA-9fw6-xgg2-mq9q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134457 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134457 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/HyNetworks/hysteria/security/advisories/GHSA-9fw6-xgg2-mq9q
- https://www.vulncheck.com/advisories/hysteria-2.5.0-before-2.8.2-quic-packet-oom-via-sniff-crypto-length
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134457
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134457"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Go packages
  • Severity7.1/10CVSS 7.1
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 32 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · HyNetworks/hysteria · Advisory GHSA-9fw6-xgg2-mq9q
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134457
RecordNVD · CVE-2026-134457
Other links 1
Linkvulncheck.com · advisories/hysteria-2.5.0-before-2.8.2-quic-packet-oom-via-sniff-crypto-length

Questions about CVE-2026-134457

Is CVE-2026-134457 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A user with a valid password can send a crafted QUIC packet that makes the server exhaust its memory and crash. The advisory describes the trigger as a crafted QUIC packet that is forwarded through the server.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134457?

github.com/apernet/hysteria/core/v2 (Go): from 2.5.0 before 2.8.2.

Source: cve.now feed data

Am I affected, and how do I check?

Hysteria versions 2.5.0 through 2.8.1 are affected, but only when the server has sniffing enabled. To check, look at the Hysteria server version and whether sniffing is turned on in the server configuration.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134457?

Upgrade the Hysteria server to version 2.8.2, which is the fixed version named in the advisory.

Source: vulncheck.com, github.com

No corrections so far. Something wrong on this page? Report an error.