# CVE-2025-23406: Denial of service in Cente IPv6

> An out-of-bounds read in Cente middleware allows attackers to crash the system via crafted TCP packets, affecting industrial network devices.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-fx9r-hc7v-rfjw

## What is CVE-2025-23406?

CVE-2025-23406 is a medium-severity denial of service vulnerability in DMG MORI Digital Co., LTD. and NXTech Co., Ltd. Cente IPv6, published on 14 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Out-of-bounds read vulnerability caused by improper checking of TCP MSS option values exists in Cente middleware TCP/IP Network Series, which may lead to processing a specially crafted packet to cause the affected product crashed.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2025-23406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23406 is a medium-severity denial of service vulnerability in DMG MORI Digital Co., LTD. and NXTech Co., Ltd. Cente IPv6, published on 14 Feb 2025. 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-23406 in the wild and no public exploit code.

Affected product: DMG MORI Digital Co., LTD. and NXTech Co., Ltd. Cente IPv6. 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-23406/ (Markdown: https://insights.sbomify.com/CVE-2025-23406/index.md)
```

## Sources

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

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