Quick answers
- Is CVE-2026-55862 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-55862 being exploited in the wild.
- How severe is CVE-2026-55862?
- Medium severity, with a CVSS score of 6.5, published 16 October 2026.
- Which products and versions are affected?
- Pupnp before 2.0.0.
- Is there a fix for CVE-2026-55862?
- Yes: fixed in 2.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-55862 attacked?
- It is attacked over the network or from the adjacent network.
- Am I affected by CVE-2026-55862?
- 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.0
Technical details
The vulnerability exists in multiple ixml DOM traversal functions (ixmlPrintDomTreeRecursive, ixmlNode_getElementsByTagNameRecursive, ixmlNode_getElementsByTagNameNSRecursive, ixmlNode_cloneNodeTreeRecursive, and ixmlNode_isAncestor) that recursively process firstChild and nextSibling links without bounds. An unauthenticated peer on the local network can supply deeply nested XML via SOAP to exhaust a service thread's stack and trigger a crash. The fix converts all five functions from recursive to iterative using fence-based traversal patterns.
Affected products
- pupnp pupnp before 2.0.0
Timeline
- 2026-10-16: disclosed
- 2026-06-15: patched