ETK-2026-194Zero's internal tracking ID, independent of the CVE number.

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

GHSA-53rm-773f-4q8c ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rust:quinn-proto >= 0.11.0, <= 0.11.18
fixed in 0.11.19
CWE-358 Improperly Implemented Security Check for Standard
ETK-2026-194, no cve assigned
pkg:cargo/quinn-proto
20d 10h 51msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −21dwaiting for further signals−20d
−15d
−10d
−5d
0

description

quinn-proto mishandles MAX_STREAM_DATA frames for peer-initiated bidirectional streams whose IDs exceed the advertised stream limit. After completing the handshake, a peer can cause an affected client or server that accepts bidirectional streams to create and return excessive streams, potentially exhausting resources or disrupting service.

mitigation

Upgrade quinn-proto to version 0.11.19 or later. Prioritize systems that accept bidirectional streams from unauthenticated or otherwise untrusted peers.

fixed in 0.11.19

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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-09-30 07:34Z

this entry in the feed

GET /api/v1/feed/ETK-2026-194

{
  "etk_id": "ETK-2026-194",
  "cve_id": null,
  "display_id": "ETK-2026-194",
  "ghsa_id": "GHSA-53rm-773f-4q8c",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Stream-limit validation flaw in quinn-proto",
  "summary": "quinn-proto mishandles MAX_STREAM_DATA frames for peer-initiated bidirectional streams whose IDs exceed the advertised stream limit. After completing the handshake, a peer can cause an affected client or server that accepts bidirectional streams to create and return excessive streams, potentially exhausting resources or disrupting service.",
  "mitigation": "Upgrade quinn-proto to version 0.11.19 or later. Prioritize systems that accept bidirectional streams from unauthenticated or otherwise untrusted peers.",
  "vendor": "rust",
  "product": "rust:quinn-proto",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.11.0, <= 0.11.18"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "0.11.19"
      ],
      "package_name": "quinn-proto",
      "purl": "pkg:cargo/quinn-proto"
    }
  ],
  "cwes": [
    358
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.864900983333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T07:34:11+00:00",
      "days": -21.074181383854167,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T09:21:00.296116+00:00",
      "url": "https://github.com/quinn-rs/quinn/security/advisories/GHSA-53rm-773f-4q8c"
    }
  }
}

published 2026-10-01 02:31Z
last change 2026-10-21 09:11Z

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.