cve.bz

CVE-2026-107159 miniupnp project miniupnpd: Divide By Zero

7.1 highEPSS 0.5%

High (7.1) in miniupnp project miniupnpd. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
MiniUPnPd through 2.3.11 built with --strict contains a divide-by-zero vulnerability in ProcessSSDPData() that allows unauthenticated local network attackers to crash the daemon. Attackers can send a single multicast M-SEARCH datagram with MX: 0 and a known ST to port 1900, triggering SIGFPE and denying UPnP IGD service.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. 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-369 Divide By Zero
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-107159 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107159?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107159?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-107159 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

  • miniupnp project:miniupnpd

Versions

From the CNA's record in the CVE List.

ProductAffected
miniupnp project miniupnpdthrough 2.3.11

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14miniupnpdno fix listedDEBIAN-CVE-2026-107159
Ubuntu26.10, Pro:16.04:LTS, Pro:18.04:LTS and 4 moreminiupnpdno fix listedUBUNTU-CVE-2026-107159

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.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • azuk4r/CVE-2026-107159 Harbor Check: matches CVE 1 star, Python, created
    MiniUPnPd <= 2.3.11 Divide-by-Zero DoS via SSDP M-SEARCH MX Header

References

Check your stackJSON