# CVE-2025-52222: Memory corruption in n/a

> Attackers can cause a Denial of Service on D-Link routers via crafted requests exploiting a buffer overflow in the radius_asp function.

- **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:** 8 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-gw2h-8xgr-6x93

## What is CVE-2025-52222?

CVE-2025-52222 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link DI-8003 v16.07.26A1, DI-8500 v16.07.26A1; DI-8003G v17.12.21A1, DI-8200G v17.12.20A1, DI-8200 v16.07.26A1, DI-8400 v16.07.26A1, DI-8004w v16.07.26A1, DI-8100 v16.07.26A1, and DI-8100G v17.12.20A1 were discovered to contain a buffer overflow via the rd_en, rd_auth, rd_acct, http_hadmin, http_hadminpwd, rd_key, and rd_ip parameters in the radius_asp function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted request.

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

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

It affects 9 products.


Products: Dlink Di-8003 Firmware, Dlink Di-8003g Firmware, Dlink Di-8004w Firmware, Dlink Di-8100 Firmware, Dlink Di-8100g Firmware, Dlink Di-8200 Firmware, Dlink Di-8200g Firmware, Dlink Di-8400 Firmware, Dlink Di-8500 Firmware.

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

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

## Is CVE-2025-52222 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-11047](https://insights.sbomify.com/CVE-2024-11047/): D-Link DI-8003 upgrade_filter.asp upgrade_filter_asp stack-based overflow (high 8.7)
- [CVE-2024-11048](https://insights.sbomify.com/CVE-2024-11048/): D-Link DI-8003 dbsrv.asp dbsrv_asp stack-based overflow (high 8.7)
- [CVE-2025-50644](https://insights.sbomify.com/CVE-2025-50644/): Memory corruption in n/a (high 7.5)
- [CVE-2025-50645](https://insights.sbomify.com/CVE-2025-50645/): Memory corruption in n/a (high 7.5)
- [CVE-2025-50646](https://insights.sbomify.com/CVE-2025-50646/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52222 is a high-severity memory corruption vulnerability in n/a, published on 8 Apr 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-52222 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-52222/ (Markdown: https://insights.sbomify.com/CVE-2025-52222/index.md)
```

## Sources

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

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