{"answers":{"affected":"3 open source packages ship an affected version, including bandit.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42788 exists.","fix":"Upgrade bandit to 1.11.0 or later.","what":"CVE-2026-42788 is a medium-severity denial of service vulnerability in mtrudel bandit, published on 1 May 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-42788 and fix it if it is affected.\n\nWhat it is: CVE-2026-42788 is a medium-severity denial of service vulnerability in mtrudel bandit, published on 1 May 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-42788 exists.\n\nAffected packages and fixed versions:\n- bandit (Hex): affected from 0.3.5; fixed in 1.11.0\n- bandit (Hex): affected from 0.3.5; fixed in 1.11.0\n- bandit (Hex): affected from 0.3.6; fixed in 1.11.0\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-42788/ (Markdown: https://insights.sbomify.com/CVE-2026-42788/index.md)","id":"CVE-2026-42788","markdown":"https://insights.sbomify.com/CVE-2026-42788/index.md","name":"CVE-2026-42788","record":{"aliases":["EEF-CVE-2026-42788","GHSA-q6v9-r226-v65f"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir HTTP/2 server","requires_auth":"none","summary":"Unauthenticated attackers can cause memory exhaustion and denial of service by sending oversized HTTP/2 frames that bypass size limits.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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 unauthenticated memory exhaustion via oversized HTTP/2 frames.\n\n'Elixir.Bandit.HTTP2.Frame':deserialize/2 in lib/bandit/http2/frame.ex checks the SETTINGS_MAX_FRAME_SIZE limit only after pattern-matching payload::binary-size(length), which requires the entire frame body to be present in memory before either the accept or reject clause can fire. A peer that announces a frame length up to the 24-bit maximum (~16 MiB) causes the server to buffer that entire body before the size guard is evaluated, regardless of the max_frame_size negotiated during the HTTP/2 handshake (default 16 KiB per RFC 9113).\n\nAn unauthenticated attacker holding many concurrent connections can force the server to buffer far more memory than the negotiated frame size limit should permit, leading to memory pressure and potential denial of service.\n\nThis issue affects bandit: from 0.3.6 before 1.11.0.","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 frame size limit checked after body is buffered in bandit","id":"CVE-2026-42788","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Non-CA certificate accepted as intermediate issuer in public_key path validation","id":"CVE-2026-42789"},"packages":[{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["0.3.5"],"last_affected":[],"package":"bandit","purl":null,"source":"GHSA-q6v9-r226-v65f"},{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["0.3.5"],"last_affected":[],"package":"bandit","purl":"pkg:hex/bandit","source":"GHSA-q6v9-r226-v65f"},{"ecosystem":"Hex","fixed":["1.11.0"],"introduced":["0.3.6"],"last_affected":[],"package":"bandit","purl":"pkg:hex/bandit","source":"EEF-CVE-2026-42788"}],"prev":{"headline":"WebSocket fragmented message reassembly unbounded in bandit","id":"CVE-2026-42786"},"products":["bandit"],"published":"2026-05-01","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":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05-27","vendors":["mtrudel"]},"summary":"Unauthenticated attackers can cause memory exhaustion and denial of service by sending oversized HTTP/2 frames that bypass size limits.","url":"https://insights.sbomify.com/CVE-2026-42788/"}