---
id: "CVE-2026-57487"
kind: "vulnerability"
aliases: ["CVE-2026-57487"]
title: "pupnp: chunked HTTP bodies bypass size limit, enabling memory exhaustion"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: [{"name": "pupnp project pupnp", "fixed": ["2.0.2"], "affected": "< 2.0.2", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["c", "embedded", "iot", "package", "pupnp", "upnp"]
not_affected_if: ["pupnp-2.0.2-or-later"]
published_at: "2026-10-16T16:18:44+00:00"
first_seen_at: "2026-10-23T21:57:13+00:00"
updated_at: "2026-10-25T03:24:58+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57487", "first_seen_at": "2026-10-23T21:57:13+00:00"}]
---

# pupnp: chunked HTTP bodies bypass size limit, enabling memory exhaustion

pupnp'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, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:pupnp project pupnp affected < 2.0.2 fixed 2.0.2

## How to check

- Check the installed pupnp version; `unknown` for the exact command, the sources do not say how it is packaged.
- Look for pupnp in your device or control point builds that use the UPnP SDK.

## Fix

- Upgrade pupnp to `2.0.2` or later.

## Timeline

- 2026-10-23T21:57:13+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-57487

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_