Skip to main content
Menu
CVEs

Hysteria denial of service in HTTP sniff header handling

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

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.9.2
Who is exposed
Not reported

Summary

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.

Who should check

Teams running HyNetworks hysteria servers from 2.5.0 before 2.9.2 that have the HTTP sniff feature enabled.

“Hysteria 2.5.0 before 2.9.2”

vulncheck.com

What to do

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-134456 (Hysteria 2.5.0 before 2.9.2 Denial of Service via HTTP Sniff Header), 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-134456 (entry last updated 2026-11-21):
Affected:
- HyNetworks hysteria: from 2.5.0, fixed in 2.9.2
Fixed versions: 2.9.2.
Conditions (all must be true for the bug to be hit):
- Hysteria version 2.5.0 up to but not including 2.9.2. (source: https://www.vulncheck.com/advisories/hysteria-2.5.0-before-2.9.2-denial-of-service-via-http-sniff-header)
- The HTTP sniff feature is enabled in the server config. (source: https://github.com/HyNetworks/hysteria/security/advisories/GHSA-jqc5-2p7q-fqfc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-134456 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134456 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-jqc5-2p7q-fqfc
- https://www.vulncheck.com/advisories/hysteria-2.5.0-before-2.9.2-denial-of-service-via-http-sniff-header
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-134456
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-134456"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

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-jqc5-2p7q-fqfc
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134456
RecordNVD · CVE-2026-134456
Other links 1
Linkvulncheck.com · advisories/hysteria-2.5.0-before-2.9.2-denial-of-service-via-http-sniff-header

Questions about CVE-2026-134456

Is CVE-2026-134456 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 remote attacker can send HTTP headers that are oversized and never terminated, which exhausts server memory and crashes the server with out-of-memory errors, causing denial of service.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134456?

hysteria: from 2.5.0 before 2.9.2.

Source: cve.now feed data

Am I affected, and how do I check?

Hysteria versions from 2.5.0 up to but not including 2.9.2 are affected, but only when the HTTP sniff feature is enabled in the server config (sniff enable: true). To check, look at the Hysteria version reported by the server binary and at the sniff setting in the server configuration file.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134456?

The facts provided do not name a fixed version or patch identifiers beyond the affected range ending before 2.9.2, so consult the vendor's advisory for the exact upgrade target. Until the vendor confirms the fix, the workaround is to disable the HTTP sniff feature in the server config.

Source: vulncheck.com, github.com

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