{"answers":{"affected":"2 open source packages ship an affected version, including io.netty:netty-codec-http3. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42582 exists.","fix":"Upgrade io.netty:netty-codec-http3 to 4.2.13.Final or later.","what":"CVE-2026-42582 is a high-severity denial of service vulnerability in Netty Netty, published on 13 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-42582 and fix it if it is affected.\n\nWhat it is: CVE-2026-42582 is a high-severity denial of service vulnerability in Netty Netty, published on 13 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-42582 exists.\n\nAffected packages and fixed versions:\n- io.netty:netty-codec-http3 (Maven): affected from 4.2.0.Final; fixed in 4.2.13.Final\n- io.netty:netty-codec-http3 (Maven): affected from 4.2.0.Final; fixed in 4.2.13.Final\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-42582/ (Markdown: https://insights.sbomify.com/CVE-2026-42582/index.md)","id":"CVE-2026-42582","markdown":"https://insights.sbomify.com/CVE-2026-42582/index.md","name":"CVE-2026-42582","record":{"aliases":["CLEANSTART-2026-CH03473","CLEANSTART-2026-CL78657","CLEANSTART-2026-HC86648","DEBIAN-CVE-2026-42582","ECHO-bdc7-f9f5-fd1d","GHSA-2c5c-chwr-9hqw","MINI-7xv9-rhpr-rp92","MINI-ch5g-c25g-hgrg","MINI-cqgr-7v8c-w3qg","MINI-px39-fg7c-mjjq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Netty HTTP/3 library","requires_auth":"none","summary":"Attackers can cause denial of service in Netty HTTP/3 by sending crafted headers that trigger unbounded memory allocation during decoding.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"netty","vendor":"netty"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"},{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final, when decoding header blocks, the non-Huffman branch of io.netty.handler.codec.http3.QpackDecoder#decodeHuffmanEncodedLiteral may execute new byte[length] for a string literal before verifying that length bytes are actually present in the compressed field section. The wire encoding allows a very large length to be expressed in few bytes. There is no check that length \u003c= in.readableBytes() before new byte[length]. This vulnerability is fixed in 4.2.13.Final.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Netty: HTTP/3 QPACK literal unbounded allocation","id":"CVE-2026-42582","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"netty:netty","products":["netty:netty"],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Netty: Lz4FrameDecoder resource exhaustion","id":"CVE-2026-42583"},"packages":[{"ecosystem":"Maven","fixed":["4.2.13.Final"],"introduced":["4.2.0.Final"],"last_affected":[],"package":"io.netty:netty-codec-http3","purl":null,"source":"GHSA-2c5c-chwr-9hqw"},{"ecosystem":"Maven","fixed":["4.2.13.Final"],"introduced":["4.2.0.Final"],"last_affected":[],"package":"io.netty:netty-codec-http3","purl":"pkg:maven/io.netty/netty-codec-http3","source":"GHSA-2c5c-chwr-9hqw"}],"prev":{"headline":"Netty: HTTP/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization","id":"CVE-2026-42581"},"products":["netty","netty-codec-http3"],"published":"2026-05-13","related":[{"cvss_score":9.1,"headline":"Netty: SNI Routing Bypass via Fragmented TLS ClientHello Causing Fallback to Default SslContext","id":"CVE-2026-75595","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.7,"headline":"Netty: Fragmented ClientHello records trigger quadratic pre-handshake reassembly in default SNI parsing","id":"CVE-2026-75596","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.7,"headline":"Netty Bzip2Decoder: Infinite Loop in RLE State Machine Leads to Event-Loop Thread Hang","id":"CVE-2026-59901","kev_date_added":null,"published":"2026-07-29"},{"cvss_score":8.7,"headline":"Netty codec-haproxy: Signed-Byte Sentinel Collision in HAProxyMessageDecoder Leads to Unbounded Memory Exhaustion","id":"CVE-2026-55851","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.7,"headline":"Netty SpdyHttpDecoder: ByteBuf Reference Leak on RST_STREAM Leads to Native Memory Exhaustion","id":"CVE-2026-56745","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":8.7,"headline":"Netty Vulnerable to DNS Cache Poisoning via Missing Bailiwick Checks in CNAME Records","id":"CVE-2026-45674","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":8.7,"headline":"Netty has Insufficient Bailiwick Validation for NS Records","id":"CVE-2026-47691","kev_date_added":null,"published":"2026-06-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-13","vendors":["io.netty","netty"]},"summary":"Attackers can cause denial of service in Netty HTTP/3 by sending crafted headers that trigger unbounded memory allocation during decoding.","url":"https://insights.sbomify.com/CVE-2026-42582/"}