CVE-2026-134456

waiting for further signalsZero needs more public information before it can validate it.

GHSA-f7x5-74v8-6r5v ↗EUVD-2026-132472 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
HyNetworks hysteria >= 2.5.0, < 2.9.2
fixed in 2.9.2
ETK-2026-5157Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 31msince last run
55mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h47m
0
+2h
+6h
+8h
+10h
+12h

description

Hysteria versions 2.5.0 through versions before 2.9.2 do not enforce a size limit when processing HTTP headers in the HTTP sniff path. A remote unauthenticated attacker can consume server memory and crash the process by maintaining an oversized header; the service must be reachable through the affected sniffing path.

mitigation

Upgrade Hysteria to version 2.9.2 or later. Until upgrading, restrict untrusted network access to services that expose the HTTP sniffing path.

fixed in 2.9.2

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
55m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-21 16:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-21 16:32Z
    ghsa: trigger signal, started the run
  2. 2026-11-21 16:32Z

this entry in the feed

GET /api/v1/feed/CVE-2026-134456

{
  "etk_id": "ETK-2026-5157",
  "cve_id": "CVE-2026-134456",
  "display_id": "CVE-2026-134456",
  "ghsa_id": "GHSA-f7x5-74v8-6r5v",
  "euvd_id": "EUVD-2026-132472",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded HTTP header denial of service in Hysteria",
  "summary": "Hysteria versions 2.5.0 through versions before 2.9.2 do not enforce a size limit when processing HTTP headers in the HTTP sniff path. A remote unauthenticated attacker can consume server memory and crash the process by maintaining an oversized header; the service must be reachable through the affected sniffing path.",
  "mitigation": "Upgrade Hysteria to version 2.9.2 or later. Until upgrading, restrict untrusted network access to services that expose the HTTP sniffing path.",
  "vendor": "HyNetworks",
  "product": "hysteria",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.5.0, < 2.9.2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.9.2"
      ],
      "package_name": "hysteria",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 54.60403298333333,
  "t0_at": "2026-11-21T16:32:51.900000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-21T16:32:51.900000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-21T16:32:51.900000+00:00",
      "url": "https://github.com/advisories/GHSA-f7x5-74v8-6r5v"
    }
  }
}

published 2026-11-21 19:25Z
last change 2026-11-21 23:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.