{"answers":{"affected":"1 open source package ship an affected version, including bandit.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74836 exists.","fix":"Upgrade bandit to 1.12.5 or later.","what":"CVE-2026-74836 is a high-severity denial of service vulnerability in mtrudel bandit, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74836 and fix it if it is affected.\n\nWhat it is: CVE-2026-74836 is a high-severity denial of service vulnerability in mtrudel bandit, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74836 exists.\n\nAffected packages and fixed versions:\n- bandit (Hex): affected from 0.3.4; fixed in 1.12.5\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-74836/ (Markdown: https://insights.sbomify.com/CVE-2026-74836/index.md)","id":"CVE-2026-74836","markdown":"https://insights.sbomify.com/CVE-2026-74836/index.md","name":"CVE-2026-74836","record":{"aliases":["EEF-CVE-2026-74836","GHSA-fv6j-9p8m-c3wr","GHSA-xj8g-532w-jv94"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir HTTP server","requires_auth":"none","summary":"An unauthenticated remote attacker can exhaust server resources by pinning HTTP/2 stream processes indefinitely via connection-level flow control starvation.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Allocation of Resources Without Limits or Throttling vulnerability in mtrudel bandit allows an unauthenticated remote attacker to pin an unbounded number of HTTP/2 stream processes indefinitely via connection-level flow control. When a stream's response body outruns the HTTP/2 connection-level send window (default 65,535 bytes, shared across all streams on the connection), Bandit.HTTP2.Connection queues the remaining bytes and a reply closure in pending_sends and the stream process blocks forever inside a synchronous call to the connection process. Nothing bounds that wait and nothing purges the queue: a client RST_STREAM for the blocked stream is delivered to its mailbox but never read while it is stuck inside the call, so cancelling frees nothing, and periodic PING frames keep the transport-level read timeout from ever firing. The equivalent block on the stream-level send window is already bounded at 15 seconds; the connection-level path had no such bound.\n\nEach stalled stream pins its process, Plug state, and any resource the Plug holds across the blocked write, such as a pooled upstream connection in a reverse-proxy Plug. The attacker chooses any endpoint whose response exceeds the connection window (common for most non-trivial payloads), grants a generous stream-level window so only the connection window limits it, and keeps the connection alive with periodic PINGs; the primitive is repeatable across streams and connections at the cost of one idle socket each.\n\nThis issue affects bandit: from 0.3.4 before 1.12.5.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"HTTP/2 connection-window starvation pins Plug processes indefinitely in Bandit","id":"CVE-2026-74836","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Unbounded atom creation from client-supplied RPC field names in AshTypescript field formatter","id":"CVE-2026-74837"},"packages":[{"ecosystem":"Hex","fixed":["1.12.5"],"introduced":["0.3.4"],"last_affected":[],"package":"bandit","purl":"pkg:hex/bandit","source":"EEF-CVE-2026-74836"}],"prev":{"headline":"inets,httpd: Memory Exhaustion via Unenforced max_body_size During Chunked Body Reception","id":"CVE-2026-74835"},"products":["bandit"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-21","vendors":["mtrudel"]},"summary":"An unauthenticated remote attacker can exhaust server resources by pinning HTTP/2 stream processes indefinitely via connection-level flow control starvation.","url":"https://insights.sbomify.com/CVE-2026-74836/"}