cve.bz

CVE-2026-57486 pupnp project pupnp: NULL Pointer Dereference

7.5 highExploit referenceEPSS 0.4%Fix available

High (7.5) in pupnp project pupnp. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-57486 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57486?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57486?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57486 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
pupnp_project:pupnpbefore 2.0.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13pupnpno fix listedDEBIAN-CVE-2026-57486
Debian14pupnp1:22.1.8-2DEBIAN-CVE-2026-57486
Ubuntu16.04:LTSmediatombno fix listedUBUNTU-CVE-2026-57486
Ubuntu18.04:LTSlibupnp, pupnp-1.8no fix listedUBUNTU-CVE-2026-57486
Ubuntu20.04:LTS, 22.04:LTSpupnp-1.8no fix listedUBUNTU-CVE-2026-57486
Ubuntu24.04:LTS, 26.04:LTS, 26.10pupnpno fix listedUBUNTU-CVE-2026-57486
UbuntuPro:16.04:LTSlibupnpno fix listedUBUNTU-CVE-2026-57486

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

References

Check your stackJSON