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

> Integer truncation in HTTP Content-Length parsing allows request smuggling or denial of service in UPnP applications.

- **Severity:** High 7.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-57488, GHSA-g6c2-x4r9-352g, UBUNTU-CVE-2026-57488

## What is CVE-2026-57488?

CVE-2026-57488 is a high-severity vulnerability in pupnp, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests), CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-57488?

It affects 1 product.


Products: Pupnp Project Pupnp.

## How do I fix CVE-2026-57488?

Upgrade to a fixed version.

## Is CVE-2026-57488 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57488 exists.

## Other vulnerabilities in pupnp

- [CVE-2021-29462](https://insights.sbomify.com/CVE-2021-29462/): DNS rebinding in pupnp (high 7.6)
- [CVE-2026-57486](https://insights.sbomify.com/CVE-2026-57486/): pupnp: NULL pointer dereference in ixmlNode_compare crashes on non-namespaced attributes (high 7.5)
- [CVE-2026-57487](https://insights.sbomify.com/CVE-2026-57487/): libupnp chunked HTTP bodies can bypass g_maxContentLength and be fully buffered (high 7.5)
- [CVE-2026-77630](https://insights.sbomify.com/CVE-2026-77630/): pupnp: Denial of service via blocking DNS resolution in parse_uri()/GENA callback parsing (high 7.5)
- [CVE-2021-28302](https://insights.sbomify.com/CVE-2021-28302/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-57488 and fix it if it is affected.

What it is: CVE-2026-57488 is a high-severity vulnerability in pupnp, published on 16 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57488 exists.

Affected product: pupnp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-57488/ (Markdown: https://insights.sbomify.com/CVE-2026-57488/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57488
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57488
- OSV: https://osv.dev/vulnerability/CVE-2026-57488

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-57488/
Summaries are generated and may contain mistakes; the official description above is the record.