Skip to content
OpenAdvisories
High · 7.5 CVE-2026-57487 EUVD-2026-102929

libupnp chunked HTTP bodies can bypass g_maxContentLength and be fully buffered

Published Oct 16, 2026 · Updated Oct 21, 2026 · Assigned by GitHub_M

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->content_length at zero while parser_parse_chunky_entity and parser_parse_chunky_body accumulate decoded bytes in parser->msg.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.

Affected products

VendorProductAffectedFixed
pupnp pupnp < 2.0.2 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 pupnp 1:22.1.8-2 —
Debian 13 pupnp No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 pupnp No fix yet —
Ubuntu 26.04 LTS pupnp No fix yet —
Ubuntu 24.04 LTS pupnp No fix yet —
Ubuntu 22.04 LTS pupnp-1.8 No fix yet —
Ubuntu 20.04 LTS pupnp-1.8 No fix yet —
Show 3 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu 18.04 LTS libupnp +1 No fix yet —
Ubuntu 16.04 LTS mediatomb No fix yet —
Ubuntu Pro 16.04 LTS libupnp No fix yet —

References