Live › vulnerability › CVE-2026-57487
Go to dashboardpupnp's HTTP parser does not apply its maximum content length to chunked Transfer-Encoding bodies, so a remote peer can make the process buffer an oversized entity. The result is resource exhaustion and denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications built on pupnp before 2.0.2 that accept HTTP responses or requests over the network, such as SOAP, GENA, miniserver, or control point paths, are exposed. Systems that do not use pupnp, or that run it only on isolated networks with no untrusted peers, are less exposed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| pupnp project pupnp | vendor | < 2.0.2 | 2.0.2 |
unknown for the exact command, the sources do not say how it is packaged.2.0.2 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-57487")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.