CVE-2026-55862: pupnp: Incomplete fix for CVE-2021-28302: recursive DOM functions cause stack overflow

Published Oct 16, 2026
·
Updated

pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.0, multiple ixml DOM traversal functions process deeply nested XML with unbounded recursion. The iterative XML parser accepts the document, but ixmlPrintDomTreeRecursive in ixml/src/ixml.c and ixmlNodegetElementsByTagNameRecursive, ixmlNodegetElementsByTagNameNSRecursive, ixmlNodecloneNodeTreeRecursive, and ixmlNodeisAncestor in ixml/src/node.c recurse over firstChild and nextSibling links. An unauthenticated peer on the local network can supply deeply nested XML through a SOAP request, exhaust a service thread's stack, and crash the UPnP service. This is an incomplete-fix case for CVE-2021-28302 because its remediation converted ixmlNodefree but left these traversal paths recursive. This issue is fixed in 2.0.0.

Affected Software

1 affected component
pupnp pupnp<2.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pupnp to a version that resolves this vulnerability.

    Fixed in 2.0.0

Event History

Oct 16, 2026
CVE Published
via MITRE·03:32 PM
Data Sourced
via MITRE·03:32 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this denial-of-service issue?

UPnP services built with pupnp versions before 2.0.0 are affected when they accept SOAP requests from peers on the local network. An unauthenticated local-network peer can trigger the issue.

2

What does an attacker need to do to exploit it?

The attacker needs network access to the local network and must send a SOAP request containing deeply nested XML. No authentication or user interaction is required.

3

What is the operational impact of successful exploitation?

Deeply nested XML can exhaust the stack of a service thread through recursive ixml DOM traversal functions. This can crash the UPnP service; the provided information indicates no confidentiality or integrity impact.

4

What should be done if an immediate upgrade is not possible?

The provided data identifies upgrading to pupnp 2.0.0 as the fix. It does not provide a documented workaround or configuration mitigation.

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