CVE-2026-77630: pupnp: Denial of service via blocking DNS resolution in parse_uri()/GENA callback parsing

Published Oct 16, 2026
·
Updated

pupnp is an SDK for development of UPnP device and control point applications. Prior to 22.0.4, parsehostport in upnp/src/genlib/net/uri/uri.c synchronously calls getaddrinfo while parseuri is processing attacker-supplied hostnames from inbound HTTP request targets in upnp/src/genlib/net/http/httpparser.c and GENA SUBSCRIBE CALLBACK headers handled by createurllist in upnp/src/gena/genadevice.c. A remote unauthenticated peer can choose a slow or nonresponsive hostname and block a bounded miniserver worker for the resolver timeout, allowing a small number of requests to exhaust the thread pool and deny UPnP service. This issue is fixed in 22.0.4.

Affected Software

1 affected component
Portable UPnP Project Portable UPnP SDK<22.0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pupnp to a version that resolves this vulnerability.

    Fixed in 22.0.4

Event History

Oct 16, 2026
CVE Published
via MITRE·03:36 PM
Data Sourced
via MITRE·03:36 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial of service?

UPnP device and control point applications built with pupnp versions before 22.0.4 are affected when they process inbound HTTP request targets or GENA SUBSCRIBE CALLBACK headers containing attacker-controlled hostnames.

2

What does an attacker need to exploit this issue?

An attacker needs only network access to send crafted requests; no authentication or user interaction is required. They can supply a slow or nonresponsive hostname that causes synchronous DNS resolution to block a miniserver worker.

3

How does this lead to service disruption?

Each malicious hostname can occupy a bounded miniserver worker until the DNS resolver times out. A small number of such requests can exhaust the thread pool and prevent UPnP service from being handled.

4

What is the available fix?

Upgrade pupnp to version 22.0.4, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203