{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-57487 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-57487 is a high-severity denial of service vulnerability in pupnp, published on 16 Oct 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-57487 and fix it if it is affected.\n\nWhat it is: CVE-2026-57487 is a high-severity denial of service vulnerability in pupnp, published on 16 Oct 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-57487 in the wild and no public exploit code.\n\nAffected product: pupnp. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-57487/ (Markdown: https://insights.sbomify.com/CVE-2026-57487/index.md)","id":"CVE-2026-57487","markdown":"https://insights.sbomify.com/CVE-2026-57487/index.md","name":"CVE-2026-57487","record":{"aliases":["DEBIAN-CVE-2026-57487","GHSA-gcj7-j9f7-q84c","UBUNTU-CVE-2026-57487"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"UPnP SDK library","requires_auth":"none","summary":"Remote attackers can cause resource exhaustion and denial of service by sending chunked HTTP bodies that bypass content length limits in the pupnp library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pupnp","vendor":"pupnp_project"}],"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-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.2, Transfer-Encoding: chunked causes the HTTP parser in upnp/src/genlib/net/http/httpparser.c to leave parser-\u003econtent_length at zero while parser_parse_chunky_entity and parser_parse_chunky_body accumulate decoded bytes in parser-\u003emsg.entity. The g_maxContentLength checks in http_RecvMessage in upnp/src/genlib/net/http/httpreadwrite.c therefore reject oversized numeric Content-Length bodies but do not enforce the same limit on decoded chunked bodies. A remote peer that can reach a SOAP, GENA, miniserver, or control-point HTTP response path can make the process buffer an entity larger than the configured maximum, causing resource exhaustion and denial of service. This issue is fixed in 2.0.2.","ecosystems":[],"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":"libupnp chunked HTTP bodies can bypass g_maxContentLength and be fully buffered","id":"CVE-2026-57487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"pupnp: Integer truncation in HTTP Content-Length parsing enables request smuggling","id":"CVE-2026-57488"},"packages":[],"prev":{"headline":"pupnp: NULL pointer dereference in ixmlNode_compare crashes on non-namespaced attributes","id":"CVE-2026-57486"},"products":["pupnp"],"published":"2026-10-16","related":[{"cvss_score":7.6,"headline":"DNS rebinding in pupnp","id":"CVE-2021-29462","kev_date_added":null,"published":"2021-04-20"},{"cvss_score":7.5,"headline":"pupnp: NULL pointer dereference in ixmlNode_compare crashes on non-namespaced attributes","id":"CVE-2026-57486","kev_date_added":null,"published":"2026-10-16"},{"cvss_score":7.5,"headline":"pupnp: Denial of service via blocking DNS resolution in parse_uri()/GENA callback parsing","id":"CVE-2026-77630","kev_date_added":null,"published":"2026-10-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-28302","kev_date_added":null,"published":"2021-03-12"},{"cvss_score":7.1,"headline":"pupnp: Integer truncation in HTTP Content-Length parsing enables request smuggling","id":"CVE-2026-57488","kev_date_added":null,"published":"2026-10-16"},{"cvss_score":6.5,"headline":"pupnp: Incomplete fix for CVE-2021-28302: recursive DOM functions cause stack overflow","id":"CVE-2026-55862","kev_date_added":null,"published":"2026-10-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-10-21","vendors":["pupnp"]},"summary":"Remote attackers can cause resource exhaustion and denial of service by sending chunked HTTP bodies that bypass content length limits in the pupnp library.","url":"https://insights.sbomify.com/CVE-2026-57487/"}