CVE-2026-57488
Received Received - Intake

Integer Overflow in Pupnp HTTP Content-Length Parsing

Vulnerability report for CVE-2026-57488, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
pupnp pupnp < 2.0.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
CWE-444 The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability exists in the pupnp library versions prior to 2.0.2. It involves incorrect parsing of the HTTP Content-Length header in the raw_to_int function. The function uses strtol to parse the header value, which returns a 64-bit long, but then casts it to a 32-bit int. On 64-bit systems, values larger than INT_MAX get truncated, causing the parser to misinterpret the actual body length. This can lead to request smuggling or denial of service.

Detection Guidance

Check if your system uses pupnp versions prior to 2.0.2 by running commands like 'pkg-config --modversion libupnp' or 'dpkg -l | grep libupnp' on Linux. Inspect HTTP traffic for Content-Length headers with values exceeding INT_MAX (2147483647) using tools like tcpdump or Wireshark. Monitor for request smuggling attempts or unusual parsing behavior in UPnP devices.

Impact Analysis

An attacker on the local network can exploit this to cause denial of service by making a worker wait for an extremely large body that never arrives. They can also perform request smuggling, where the parser reads only part of the body and treats the rest as a new request, potentially bypassing security controls or manipulating downstream services.

Compliance Impact

This vulnerability primarily impacts availability and integrity of UPnP services, which could indirectly affect compliance with standards like GDPR or HIPAA by enabling denial-of-service conditions or request smuggling that might bypass security controls. However, the direct impact on compliance depends on how UPnP services are used in systems handling regulated data.

Mitigation Strategies

Upgrade to pupnp version 2.0.2 or later immediately. If upgrading is not possible, apply the patch from the upstream commit de9602aef34ff722f3630d66c9be8eaa0aa9f012. Disable UPnP services if unused or restrict network access to UPnP devices to trusted networks only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-57488. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart