{"answers":{"affected":"2 open source packages ship an affected version, including io.netty:netty-codec-http3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44892 in the wild and no public exploit code.","fix":"Upgrade io.netty:netty-codec-http3 to 4.2.15.Final or later.","what":"CVE-2026-44892 is a high-severity denial of service vulnerability in Netty Netty, published on 12 Jun 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-44892 and fix it if it is affected.\n\nWhat it is: CVE-2026-44892 is a high-severity denial of service vulnerability in Netty Netty, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44892 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.netty:netty-codec-http3 (Maven): affected from 4.2.0.Final; fixed in 4.2.15.Final\n- io.netty:netty-codec-http3 (Maven): affected from 4.2.0.Final; fixed in 4.2.15.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-44892/ (Markdown: https://insights.sbomify.com/CVE-2026-44892/index.md)","id":"CVE-2026-44892","markdown":"https://insights.sbomify.com/CVE-2026-44892/index.md","name":"CVE-2026-44892","record":{"aliases":["CLEANSTART-2026-WM08023","DEBIAN-CVE-2026-44892","ECHO-9191-378f-b096","GHSA-c2rx-5r8w-8xr2","MINI-5v2m-wfc4-pwhp","MINI-7gx6-fc2m-2r2v","MINI-cg9c-ghmq-ch97","MINI-h93h-q9gw-27vf","MINI-p93v-r494-p3hh","MINI-qrpw-q36h-6xwf","MINI-vh3c-2r3q-63q5","MINI-xxhq-j822-pv9w","UBUNTU-CVE-2026-44892"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java network framework","requires_auth":"none","summary":"Netty's HTTP/3 codec lacks a default header size limit, allowing attackers to cause memory exhaustion and denial of service.","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-400","name":"Uncontrolled Resource Consumption"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Netty is a network application framework for development of protocol servers and clients. Prior to version 4.2.15.Final, the default configuration of the `Http3ConnectionHandler` in the Netty HTTP/3 codec lacks an enforced maximum header size limit. When a peer does not explicitly specify `HTTP3_SETTINGS_MAX_FIELD_SECTION_SIZE`, the implementation defaults to an unbounded limit. This insecure default configuration allows a malicious client or server to send an enormous number of headers, leading to a memory exhaustion Denial of Service via an `OutOfMemoryError`. Version 4.2.15.Final contains a patch.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Netty has a Vulnerable Default Configuration Which Leads to Denial of Service via Unbounded HTTP/3 Header Size","id":"CVE-2026-44892","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":2,"next":{"headline":"Netty: HAProxy SSL TLV parsing leaks retained slice on invalid TLV length","id":"CVE-2026-44893"},"packages":[{"ecosystem":"Maven","fixed":["4.2.15.Final"],"introduced":["4.2.0.Final"],"last_affected":[],"package":"io.netty:netty-codec-http3","purl":null,"source":"GHSA-c2rx-5r8w-8xr2"},{"ecosystem":"Maven","fixed":["4.2.15.Final"],"introduced":["4.2.0.Final"],"last_affected":[],"package":"io.netty:netty-codec-http3","purl":"pkg:maven/io.netty/netty-codec-http3","source":"GHSA-c2rx-5r8w-8xr2"}],"prev":{"headline":"Netty: Denial of Service via Unbounded Headers in StompSubframeDecoder","id":"CVE-2026-44891"},"products":["netty"],"published":"2026-06-12","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-12","vendors":["netty"]},"summary":"Netty's HTTP/3 codec lacks a default header size limit, allowing attackers to cause memory exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-44892/"}