{"answers":{"affected":"3 open source packages ship an affected version, including hackney. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47073 exists.","fix":"Upgrade hackney to 4.0.1 or later.","what":"CVE-2026-47073 is a high-severity denial of service vulnerability in benoitc hackney, published on 25 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-47073 and fix it if it is affected.\n\nWhat it is: CVE-2026-47073 is a high-severity denial of service vulnerability in benoitc hackney, published on 25 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-47073 exists.\n\nAffected packages and fixed versions:\n- hackney (Hex): affected from 2.0.0; fixed in 4.0.1\n- hackney (Hex): affected from 2.0.0; fixed in 4.0.1\n- hackney (Hex): affected from 2.0.0; fixed in 4.0.1\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-47073/ (Markdown: https://insights.sbomify.com/CVE-2026-47073/index.md)","id":"CVE-2026-47073","markdown":"https://insights.sbomify.com/CVE-2026-47073/index.md","name":"CVE-2026-47073","record":{"aliases":["EEF-CVE-2026-47073","GHSA-q8jg-fgj4-fphf"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Erlang HTTP client","requires_auth":"none","summary":"A malicious WebSocket server can cause unbounded memory consumption in the hackney client, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[{"product":"hackney","vendor":"benoitc"}],"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-400","name":"Uncontrolled Resource Consumption"}],"description":"Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The WebSocket client in src/hackney_ws.erl imposes no upper bound on memory consumption in three code paths. First, read_handshake_response/3 accumulates received bytes into a growing buffer with no size cap; the per-receive timeout resets on every chunk, so a server that streams bytes without ever sending \\r\\n\\r\\n causes the buffer to grow until memory is exhausted. Second, parse_payload/9 and parse_active_payload/8 do not validate the declared frame payload length against any limit; because RFC 6455 allows payload lengths up to 2^63-1 bytes, a server that announces a very large frame and dribbles bytes causes the accumulation buffer to grow until OOM. Third, the frag_buffer field in #ws_data{} accumulates continuation frames indefinitely; a server that sends an endless stream of non-final (nofin) fragmented frames without ever sending a final (fin) frame grows frag_buffer without bound.\n\nIn all three cases the attacker only needs to control the WebSocket server the hackney client connects to, with no authentication or special client configuration required.\n\nThis issue affects hackney: from 2.0.0 before 4.0.1.","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":"Unbounded memory consumption in WebSocket client in hackney","id":"CVE-2026-47073","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":"ex_aws_sns SigningCertURL not validated in verify_message/1","id":"CVE-2026-47074"},"packages":[{"ecosystem":"Hex","fixed":["4.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"hackney","purl":"pkg:hex/hackney","source":"EEF-CVE-2026-47073"},{"ecosystem":"Hex","fixed":["4.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"hackney","purl":null,"source":"GHSA-q8jg-fgj4-fphf"},{"ecosystem":"Hex","fixed":["4.0.1"],"introduced":["2.0.0"],"last_affected":[],"package":"hackney","purl":"pkg:hex/hackney","source":"GHSA-q8jg-fgj4-fphf"}],"prev":{"headline":"CRLF injection in WebSocket upgrade request in hackney","id":"CVE-2026-47072"},"products":["hackney"],"published":"2026-05-25","related":[{"cvss_score":8.7,"headline":"Infinite loop in Alt-Svc header parser in hackney","id":"CVE-2026-47066","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":8.7,"headline":"Atom table exhaustion via unrecognized URL schemes in hackney","id":"CVE-2026-47067","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":8.2,"headline":"SOCKS5 TLS upgrade ignores caller timeout in hackney","id":"CVE-2026-47071","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":8.2,"headline":"Unbounded body accumulation in HTTP/3 response loop in hackney","id":"CVE-2026-47077","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":6.9,"headline":"CRLF injection in WebSocket upgrade request in hackney","id":"CVE-2026-47072","kev_date_added":null,"published":"2026-05-25"},{"cvss_score":6.9,"headline":"SSRF allowlist bypass via percent-encoded host in hackney","id":"CVE-2026-47076","kev_date_added":null,"published":"2026-05-25"}],"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":"US public information, NVD API terms","name":"NVD"},{"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":["benoitc"]},"summary":"A malicious WebSocket server can cause unbounded memory consumption in the hackney client, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-47073/"}