---
id: "CVE-2026-57486"
kind: "vulnerability"
aliases: ["CVE-2026-57486"]
title: "pupnp: NULL attribute field crash when removing XML attributes"
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", "upnp"]
not_affected_if: ["no-untrusted-xml", "pinned-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:25:00+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57486", "first_seen_at": "2026-10-23T21:57:13+00:00"}]
---

# pupnp: NULL attribute field crash when removing XML attributes

pupnp, a C SDK for UPnP devices and control points, dereferences NULL fields in ixmlNode_compare when comparing two non-namespaced XML attributes with the same name. An attacker who can feed crafted XML into an application using ixmlElement_removeAttributeNode can crash the process.

_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 pupnp version your application links against; affected versions are below `2.0.2`.
- Search your code for calls to `ixmlElement_removeAttributeNode` and `ixmlDocument_createAttribute` fed by network-received XML.

## 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-57486

## From the sources

pupnp is an SDK for development of UPnP device and control point applications. Prior to 2.0.2, ixmlNode_compare in ixml/src/node.c passes the nullable nodeValue, namespaceURI, prefix, and localName fields directly to strcmp. Non-namespaced attributes created by ixmlDocument_createAttribute legitimately leave those fields NULL. When ixmlElement_removeAttributeNode compares two distinct attribute objects with the same nodeName through find_condition_node, the pointer-identity shortcut does not apply and the comparison dereferences NULL, causing a process crash when application handling of attacker-controlled XML reaches this path. 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_