Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8

Hysteria: A specially constructed quic package can crash the server OOM when the sniff is enabled

GHSA-9fw6-xgg2-mq9q

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/apernet/hysteria/core/v2

    Affected
    <= 2.8.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Summary A specially constructed quic package can crash the server OOM when the sniff is enabled. Details When the server has sniff enabled, a valid connection can request the server to forward UDP traffic and construct a huge crypto length. The server will allocate memory according to this length, causing an OOM. PoC server.yaml poc.go Impact When sniffing is enabled on the server, a user with a valid password can launch an attack that could cause the server to run out of memory (OOM).

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9fw6-xgg2-mq9q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-9fw6-xgg2-mq9q

Advisory: Hysteria: A specially constructed quic package can crash the server OOM when the sniff is enabled
IDs: GHSA-9fw6-xgg2-mq9q
Record: https://patchnext.com/advisories/ghsa-9fw6-xgg2-mq9q (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/apernet/hysteria/core/v2: affected <= 2.8.1

## Suggested inspection (read-only)
- Go github.com/apernet/hysteria/core/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/apernet/hysteria/core/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9fw6-xgg2-mq9q (GitHub-reviewed advisory GHSA-9fw6-xgg2-mq9q lists affected ranges: Go github.com/apernet/hysteria/core/v2 >=0 <=2.8.1)

Commands are suggestions: review each one before running it.

Loading voting…