CVE-2026-41682: pupnp · Signed to Unsigned Conversion Error
Affects pupnpSource GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.18.5 when convenient.
Data as of 27 Oct 2026, 00:43 UTC
- Patch
- Available – fixed in 1.18.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade pupnp to 1.18.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pupnp pupnp | Affected
| Fixed in
|
AI-suggested
Upgrade pupnp to version 1.18.5 or later, where this vulnerability has been patched. No other mitigation steps are indicated.
Description
pupnp versions prior to 1.18.5 contain a vulnerability involving signed to unsigned conversion error in the parse_uri() function. This flaw leads to port truncation via atoi() casting, causing SRRF port confusion. The issue has been fixed in version 1.18.5.