CVE-2026-74836
HTTP/2 connection-level flow control bug in Bandit enables resource-exhaustion DoS.
Is CVE-2026-74836 being exploited?
Not confirmed. CVE-2026-74836 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-74836?
CVE-2026-74836 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74836?
Yes. A fix has been recorded for CVE-2026-74836. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74836 affect?
CVE-2026-74836 affects bandit < 1.12.5, Elixir apps using Bandit HTTP/2, Plug-based reverse-proxies using Bandit. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74836?
Upgrade Bandit to >= 1.12.5 and/or limit HTTP/2 connection window and add throttling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attacker can stall HTTP/2 streams to pin processes and exhaust connections/resources, causing service/proxy DoS.
Immediate action required
- affected>= 0.3.4 and < 1.12.5
- affected>= 6feadb31189d18b7dcda6c663112cd3bbaf63a46 and < f6914aad14bb1365dd6f306aa592cfb0819bed3e
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.