{"answers":{"affected":"4 open source packages ship an affected version, including io.netty:netty-codec-mqtt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44248 in the wild and no public exploit code.","fix":"Upgrade io.netty:netty-codec-mqtt to a fixed version for your release line: 4.1.133.Final or 4.2.13.Final.","what":"CVE-2026-44248 is a medium-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-44248 and fix it if it is affected.\n\nWhat it is: CVE-2026-44248 is a medium-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: There is no known exploitation of CVE-2026-44248 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.netty:netty-codec-mqtt (Maven): affected all versions; fixed in 4.1.133.Final\n- io.netty:netty-codec-mqtt (Maven): affected all versions; fixed in 4.1.133.Final\n- io.netty:netty-codec-mqtt (Maven): affected from 4.2.0.Alpha1; fixed in 4.2.13.Final\n- io.netty:netty-codec-mqtt (Maven): affected from 4.2.0.Alpha1; 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-44248/ (Markdown: https://insights.sbomify.com/CVE-2026-44248/index.md)","id":"CVE-2026-44248","markdown":"https://insights.sbomify.com/CVE-2026-44248/index.md","name":"CVE-2026-44248","record":{"aliases":["CLEANSTART-2026-DB30456","CLEANSTART-2026-KV24207","CLEANSTART-2026-VC18783","DEBIAN-CVE-2026-44248","GHSA-jfg9-48mv-9qgx","MINI-85vc-vjxc-rmx8","MINI-8qc4-m9g5-677g","MINI-gx2m-mw48-j4rx","MINI-hgqc-qcjj-jxgg","MINI-j6hp-cv3p-9349","MINI-mx3x-pj44-93xj","MINI-q9j3-3g64-qhwj","RHLW-2026-48b9709ba25473be"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Netty MQTT codec","requires_auth":"none","summary":"Attackers can cause resource exhaustion in Netty MQTT applications by sending oversized property headers, leading to 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":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Netty is an asynchronous, event-driven network application framework. Prior to 4.2.13.Final and 4.1.133.Final, the MQTT 5 header Properties section is parsed and buffered before any message size limit is applied. Specifically, in MqttDecoder, the decodeVariableHeader() method is called before the bytesRemainingBeforeVariableHeader \u003e maxBytesInMessage check. The decodeVariableHeader() can call other methods which will call decodeProperties(). Effectively, Netty does not apply any limits to the size of the properties being decoded. Additionally, because MqttDecoder extends ReplayingDecoder, Netty will repeatedly re-parse the enormous Properties sections and buffer the bytes in memory, until the entire thing parses to completion. This can cause high resource usage in both CPU and memory. This vulnerability is fixed in 4.2.13.Final and 4.1.133.Final.","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: Resource exhaustion in MqttDecoder","id":"CVE-2026-44248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"netty:netty","products":["netty:netty"],"type":"denial_of_service","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Netty has an IPv6 Subnet Filter Bypass via Incorrect Comparator Masking","id":"CVE-2026-44249"},"packages":[{"ecosystem":"Maven","fixed":["4.1.133.Final"],"introduced":["0"],"last_affected":[],"package":"io.netty:netty-codec-mqtt","purl":null,"source":"GHSA-jfg9-48mv-9qgx"},{"ecosystem":"Maven","fixed":["4.1.133.Final"],"introduced":["0"],"last_affected":[],"package":"io.netty:netty-codec-mqtt","purl":"pkg:maven/io.netty/netty-codec-mqtt","source":"GHSA-jfg9-48mv-9qgx"},{"ecosystem":"Maven","fixed":["4.2.13.Final"],"introduced":["4.2.0.Alpha1"],"last_affected":[],"package":"io.netty:netty-codec-mqtt","purl":null,"source":"GHSA-jfg9-48mv-9qgx"},{"ecosystem":"Maven","fixed":["4.2.13.Final"],"introduced":["4.2.0.Alpha1"],"last_affected":[],"package":"io.netty:netty-codec-mqtt","purl":"pkg:maven/io.netty/netty-codec-mqtt","source":"GHSA-jfg9-48mv-9qgx"}],"prev":{"headline":"Volcano: Webhook server vulnerable to OOM due to unbounded HTTP request body size","id":"CVE-2026-44247"},"products":["netty","netty-codec-mqtt"],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-11","vendors":["io.netty","netty"]},"summary":"Attackers can cause resource exhaustion in Netty MQTT applications by sending oversized property headers, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-44248/"}