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

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

GHSA-fmr8-qrvr-4ww5 ↗

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.
erlang bandit >= 0.3.0, < 1.14.0
fixed in 1.14.0
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-2666Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:hex/bandit
3h 52msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −6h16mwaiting for further signals−3h52m
−6h
−2h
0

description

Bandit through 1.13.1 does not impose a default limit on concurrent HTTP/2 streams. An unauthenticated client able to establish an HTTP/2 connection can consume server memory and cause denial of service by keeping many request streams active.

mitigation

Upgrade Bandit to version 1.14.0. Until the upgrade is complete, restrict untrusted access to HTTP/2 endpoints to reduce exposure.

fixed in 1.14.0

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.
–
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
18m
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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-26 13:35Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2666",
  "cve_id": null,
  "display_id": "ETK-2026-2666",
  "ghsa_id": "GHSA-fmr8-qrvr-4ww5",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unbounded HTTP/2 stream resource exhaustion in Bandit",
  "summary": "Bandit through 1.13.1 does not impose a default limit on concurrent HTTP/2 streams. An unauthenticated client able to establish an HTTP/2 connection can consume server memory and cause denial of service by keeping many request streams active.",
  "mitigation": "Upgrade Bandit to version 1.14.0. Until the upgrade is complete, restrict untrusted access to HTTP/2 endpoints to reduce exposure.",
  "vendor": "erlang",
  "product": "bandit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.3.0, < 1.14.0"
      ],
      "ecosystem": "erlang",
      "fixed_versions": [
        "1.14.0"
      ],
      "package_name": "bandit",
      "purl": "pkg:hex/bandit"
    }
  ],
  "cwes": [
    770
  ],
  "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": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.5244242,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T13:35:41+00:00",
      "days": -0.2614273344675926,
      "is_lower_bound": true,
      "measured_at": "2026-10-26T19:52:08.364706+00:00",
      "url": "https://github.com/mtrudel/bandit/security/advisories/GHSA-fmr8-qrvr-4ww5"
    }
  }
}

published 2026-10-26 17:15Z
last change 2026-10-26 19:38Z

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.