CVE-2026-57488

published 16 Oct 2026 · updated 16 Oct 2026

pupnp: Integer truncation in HTTP Content-Length parsing enables request smuggling

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
pupnp<2.0.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-57488 severity on Zeptric[![CVE-2026-57488](https://zeptric.io/badge/cve/CVE-2026-57488.svg)](https://zeptric.io/cve/CVE-2026-57488)