# CVE-2025-66974: Denial of service in n/a

> Attackers can cause denial of service or redirect connections by sending crafted packets during the provisioning phase of the Prolink smart plug.

- **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:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-rxm9-vvwj-7wrc

## What is CVE-2025-66974?

CVE-2025-66974 is a high-severity denial of service vulnerability in n/a, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Prolink 13A Smart Plug Model Version: DS-3202M-UKv3 Wi-Fi and Application Version mEzee 2.6.7 allows attackers to cause a Denial of Service (DoS) or connection to an attacker-controlled device via supplying a crafted packet during the provisioning phase.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-66974 being exploited?

There is no known exploitation of CVE-2025-66974 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66974 is a high-severity denial of service vulnerability in n/a, published on 15 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66974 in the wild and no public exploit code.

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-66974/ (Markdown: https://insights.sbomify.com/CVE-2025-66974/index.md)
```

## Sources

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

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