Quick answers
- Is CVE-2026-57486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57486 being exploited in the wild.
- How severe is CVE-2026-57486?
- High severity, with a CVSS score of 7.5, published 16 October 2026.
- Which products and versions are affected?
- Pupnp before 2.0.2.
- Is there a fix for CVE-2026-57486?
- Yes: fixed in 2.0.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57486 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57486?
- Check whether you run Pupnp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.2
Technical details
The ixmlNode_compare function in ixml/src/node.c passes nullable fields (nodeValue, namespaceURI, prefix, localName) directly to strcmp without NULL checks. When ixmlElement_removeAttributeNode compares two distinct non-namespaced attribute objects with the same nodeName, this dereferences NULL pointers, crashing the process. The vulnerability requires the application to process attacker-controlled XML reaching the removeAttributeNode code path.
Affected products
- pupnp pupnp before 2.0.2
Timeline
- 2026-10-16: disclosed
- 2026-06-17: patched