{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57488 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-57488 is a high-severity vulnerability in pupnp, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57488 and fix it if it is affected.\n\nWhat it is: CVE-2026-57488 is a high-severity vulnerability in pupnp, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57488 exists.\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-57488/ (Markdown: https://insights.sbomify.com/CVE-2026-57488/index.md)","id":"CVE-2026-57488","markdown":"https://insights.sbomify.com/CVE-2026-57488/index.md","name":"CVE-2026-57488","record":{"aliases":["DEBIAN-CVE-2026-57488","GHSA-g6c2-x4r9-352g","UBUNTU-CVE-2026-57488"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"UPnP SDK library","requires_auth":"none","summary":"Integer truncation in HTTP Content-Length parsing allows request smuggling or denial of service in UPnP applications.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pupnp","vendor":"pupnp_project"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.2, raw_to_int in upnp/src/genlib/net/http/httpparser.c parses Content-Length with strtol and casts the resulting long to a 32-bit int before the caller stores it as unsigned int. On LP64 systems, values greater than INT_MAX can truncate or wrap, so the HTTP parser can accept a body length different from the declared value. A remote adjacent-network peer can use the resulting parser disagreement to leave bytes to be interpreted as another request in persistent or proxied contexts, or can make a worker wait for an extremely large body and cause 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":"weaponised"},"has_fix":true,"headline":"pupnp: Integer truncation in HTTP Content-Length parsing enables request smuggling","id":"CVE-2026-57488","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"FileRise: AUTH_BYPASS reverse-proxy header trust without source IP validation enables full authentication bypass","id":"CVE-2026-57489"},"packages":[],"prev":{"headline":"libupnp chunked HTTP bodies can bypass g_maxContentLength and be fully buffered","id":"CVE-2026-57487"},"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":"libupnp chunked HTTP bodies can bypass g_maxContentLength and be fully buffered","id":"CVE-2026-57487","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":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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["pupnp"]},"summary":"Integer truncation in HTTP Content-Length parsing allows request smuggling or denial of service in UPnP applications.","url":"https://insights.sbomify.com/CVE-2026-57488/"}