Hysteria denial of service in UDP fragmentation handling
Affects Hysteria servers from 1.0.0 before 2.9.2 where clients must authenticate and can advertise a very small QUIC max_datagram_frame_size. Fixed in 2.9.2.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.9.2
- Who is exposed
- Specific setups only
Summary
Written by a model
Hysteria 1.0.0 before 2.9.2 contains a denial of service vulnerability in FragUDPMessage where UDP fragmentation fails to handle headers larger than the maximum datagram payload size. Authenticated clients can advertise a small max_datagram_frame_size and trigger a UDP response, causing a slice bounds panic that crashes the server.
Who should check
Operators running Hysteria server versions 1.0.0 through 2.9.2 that accept authenticated clients, including those exposing UDP relaying.
“Affecting hysteria >= 1.0.0, < 2.9.2”
What to do
Check whether your setup matches what the bug needs.
Client must be authenticated to the Hysteria server. Client advertises a very small QUIC max_datagram_frame_size and the server then sends a UDP response.Upgrade to a fixed version: 2.9.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-134455 (Hysteria 1.0.0 before 2.9.2 Denial of Service via max_datagram_frame_size), 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-134455 (entry last updated 2026-11-21):
Affected:
- HyNetworks hysteria: from 1.0.0, fixed in 2.9.2
Fixed versions: 2.9.2.
Conditions (all must be true for the bug to be hit):
- Client must be authenticated to the Hysteria server. (source: https://github.com/HyNetworks/hysteria/security/advisories/GHSA-qh5x-rfwf-rvfv)
- Client advertises a very small QUIC max_datagram_frame_size and the server then sends a UDP response. (source: https://github.com/HyNetworks/hysteria/security/advisories/GHSA-qh5x-rfwf-rvfv)
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-134455 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134455 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/HyNetworks/hysteria/security/advisories/GHSA-qh5x-rfwf-rvfv
- https://www.vulncheck.com/advisories/hysteria-1.0.0-before-2.9.2-denial-of-service-via-max-datagram-frame-size
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-134455
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-134455"}.Affected versions
- HyNetworks hysteriaFrom 1.0.0 · fixed in 2.9.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · HyNetworks/hysteria · Advisory GHSA-qh5x-rfwf-rvfv |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134455 |
| Record | NVD · CVE-2026-134455 |
| Other links 1 | |
| Link | vulncheck.com · advisories/hysteria-1.0.0-before-2.9.2-denial-of-service-via-max-datagram-frame-size |
Questions about CVE-2026-134455
Is CVE-2026-134455 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?
An authenticated client can crash the Hysteria server process with a slice bounds panic, causing denial of service. The client does this by advertising a very small QUIC max_datagram_frame_size and then triggering a UDP response from the server.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-134455?
hysteria: from 1.0.0 before 2.9.2.
Source: cve.now feed data
Am I affected, and how do I check?
Hysteria versions from 1.0.0 up to but not including 2.9.2 are listed as affected. The crash needs an authenticated client that advertises a very small max_datagram_frame_size, followed by a UDP response from the server. A reader can compare the installed Hysteria server version against that range.
Source: github.com, vulncheck.com
How do I fix CVE-2026-134455?
Upgrade Hysteria to version 2.9.2 or later, which is the listed fixed version.
Source: github.com, vulncheck.com
Related
No corrections so far. Something wrong on this page? Report an error.