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

Severity: high (CVSS 7.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: yes
Published: 2026-10-16 · updated 2026-10-20
Weakness: CWE-190

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.

Affected products

pupnp: before 2.0.2 — fixed in 2.0.2

How to fix

Upgrade to a fixed version: pupnp 2.0.2. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-57488 or the next vulnerability affects your stack