Skip to main content
Menu
CVEs

HyNetworks Hysteria access control bypass in UDP ACL enabling SSRF

Only affects Hysteria 2.0.0 through 2.9.1 servers that have UDP ACL rules blocking destinations. Fixed in 2.9.2.

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

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.9.2
Who is exposed
Specific setups only

Summary

Written by a model

Hysteria from 2.0.0 before 2.9.2 contains an ACL bypass vulnerability that allows authenticated clients to reach blocked UDP destinations by reusing an established UDP session. Attackers can open a session to an allowed destination, then send later packets to localhost or private-network addresses to access internal-only UDP services.

Who should check

Operators running Hysteria 2.0.0 through 2.9.1 servers that use UDP ACL rules to block localhost or private-network destinations.

“Affecting hysteria >= 2.0.0, < 2.9.2”

vulncheck.com

What to do

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

    Hysteria versions from 2.0.0 before 2.9.2 (advisory lists affected as >= 2.0.0, <= 2.9.1). The server must have UDP ACL rules configured to block destinations.
  2. 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-134454 (Hysteria 2.0.0 before 2.9.2 UDP ACL Bypass Enabling SSRF), 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-134454 (entry last updated 2026-11-21):
Affected:
- Go package github.com/apernet/hysteria/core/v2: from 2.0.0, fixed in 2.9.2
Fixed versions: 2.9.2.
Conditions (all must be true for the bug to be hit):
- Hysteria versions from 2.0.0 before 2.9.2 (advisory lists affected as >= 2.0.0, <= 2.9.1). (source: https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf)
- The server must have UDP ACL rules configured to block destinations. (source: https://github.com/HyNetworks/hysteria/security/advisories/GHSA-vgrc-hq28-p3xp)
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-134454 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134454 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-vgrc-hq28-p3xp
- https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf
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-134454
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-134454"}.

Affected versions

cve.now Index

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

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 30 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-vgrc-hq28-p3xp
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134454
RecordNVD · CVE-2026-134454
Other links 1
Linkvulncheck.com · advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf

Questions about CVE-2026-134454

Is CVE-2026-134454 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?

Hysteria's UDP ACL policy meant to block certain UDP destinations is not enforced on later packets in an already established UDP session. An authenticated client can reuse that session to reach blocked UDP destinations, including localhost and private-network services that are only meant to be internal.

Source: vulncheck.com, github.com

Which versions are affected by CVE-2026-134454?

github.com/apernet/hysteria/core/v2 (Go): from 2.0.0 before 2.9.2.

Source: cve.now feed data

Am I affected, and how do I check?

Hysteria versions from 2.0.0 before 2.9.2 are affected, and the advisory lists them as 2.0.0 through 2.9.1. The issue needs a server with UDP ACL rules configured to block destinations, so check your server's Hysteria version and its ACL configuration.

Source: vulncheck.com, github.com

How do I fix CVE-2026-134454?

Upgrade the Hysteria server to 2.9.2, which is the fixed version. The advisory does not list a workaround or patch identifiers.

Source: vulncheck.com, github.com

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