CVE-2026-115269

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

GHSA-p2qv-vx88-385x ↗EUVD-2026-109819 ↗

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.
erlang bandit >= 1.4.0, < 1.14.0
fixed in 1.14.0
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-2668Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:hex/bandit
3h 19msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Bandit versions 1.4.0 through 1.13.x can fail to enforce an overall timeout while reading HTTP/2 request bodies. An unauthenticated remote client may retain HTTP/2 streams and related application resources when HTTP/2 is enabled and handlers read request bodies.

mitigation

Upgrade Bandit to version 1.14.0 or later. If an immediate upgrade is not possible, disable HTTP/2 with http_2_options: [enabled: false].

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
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-26 13:30Z
Δ 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:30Z
  2. 2026-10-26 13:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2668",
  "cve_id": "CVE-2026-115269",
  "display_id": "CVE-2026-115269",
  "ghsa_id": "GHSA-p2qv-vx88-385x",
  "euvd_id": "EUVD-2026-109819",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Bandit HTTP/2 request-body timeout resource exhaustion",
  "summary": "Bandit versions 1.4.0 through 1.13.x can fail to enforce an overall timeout while reading HTTP/2 request bodies. An unauthenticated remote client may retain HTTP/2 streams and related application resources when HTTP/2 is enabled and handlers read request bodies.",
  "mitigation": "Upgrade Bandit to version 1.14.0 or later. If an immediate upgrade is not possible, disable HTTP/2 with `http_2_options: [enabled: false]`.",
  "vendor": "erlang",
  "product": "bandit",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.4.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": 34.8913252,
  "t0_at": "2026-10-26T13:30:24.621000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T13:30:24.621000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T13:30:24.621000+00:00",
      "url": "https://github.com/mtrudel/bandit/security/advisories/GHSA-p2qv-vx88-385x"
    }
  }
}

published 2026-10-26 17:30Z
last change 2026-10-26 20: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.