# CVE-2025-2026: Other in NPort 6100-G2/6200-G2 Series

> Authenticated attackers can cause a denial of service via null byte injection in the web API of Moxa NPort devices.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 31 Dec 2025
- **Also known as:** GHSA-5vwc-hh96-8x8g

## What is CVE-2025-2026?

CVE-2025-2026 is a high-severity vulnerability in Moxa NPort 6100-G2/6200-G2 Series, published on 31 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The NPort 6100-G2/6200-G2 Series is affected by a high-severity vulnerability (CVE-2025-2026) that allows remote attackers to execute a null byte injection through the device’s web API. This may lead to an unexpected device reboot and result in a denial-of-service (DoS) condition.

An authenticated remote attacker with web read-only privileges can exploit the vulnerable API to inject malicious input. Successful exploitation may cause the device to reboot, disrupting normal operations and causing a temporary denial of service.

Weakness: CWE-170 (Improper Null Termination)

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


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

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

## Is CVE-2025-2026 being exploited?

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

Public exploit code:

- Daftar CVE 2025-2026 terupdate (github_poc): https://github.com/magercode/List-CVE-2025-2026

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2026 is a high-severity vulnerability in Moxa NPort 6100-G2/6200-G2 Series, published on 31 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2026 in the wild and no public exploit code.

Affected product: Moxa NPort 6100-G2/6200-G2 Series. 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-2026/ (Markdown: https://insights.sbomify.com/CVE-2025-2026/index.md)
```

## Sources

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

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