# CVE-2025-50681: Null dereference in n/a

> Remote attackers can crash igmpproxy via crafted IGMPv3 packets, causing denial of service on embedded networking devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** DEBIAN-CVE-2025-50681, GHSA-r9q2-28x2-qh78, UBUNTU-CVE-2025-50681

## What is CVE-2025-50681?

CVE-2025-50681 is a high-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

igmpproxy 0.4 before commit 2b30c36 allows remote attackers to cause a denial of service (application crash) via a crafted IGMPv3 membership report packet with a malicious source address. Due to insufficient validation in the `recv_igmp()` function in src/igmpproxy.c, an invalid group record type can trigger a NULL pointer dereference when logging the address using `inet_fmtsrc()`. This vulnerability can be exploited by sending malformed multicast traffic to a host running igmpproxy, leading to a crash. igmpproxy is used in various embedded networking environments and consumer-grade IoT devices (such as home routers and media gateways) to handle multicast traffic for IPTV and other streaming services. Affected devices that rely on unpatched versions of igmpproxy may be vulnerable to remote denial-of-service attacks across a LAN .

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2025-50681?

It affects 1 product.


Products: Pali Igmpproxy.

## How do I fix CVE-2025-50681?

No fix has been published for CVE-2025-50681 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-50681 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50681 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-50681 and fix it if it is affected.

What it is: CVE-2025-50681 is a high-severity vulnerability in n/a, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50681 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-50681/ (Markdown: https://insights.sbomify.com/CVE-2025-50681/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-50681
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-50681
- OSV: https://osv.dev/vulnerability/CVE-2025-50681

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-50681/
Summaries are generated and may contain mistakes; the official description above is the record.