# CVE-2025-9998: Improper validation of packets sequencing

> Attackers can cause a denial of service in PcVue by sending specially crafted packets due to improper sequence validation.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/AU:Y/R:U/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-x75f-chmc-5vjc

## What is CVE-2025-9998?

CVE-2025-9998 is a medium-severity denial of service vulnerability in arcinfo PcVue, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The sequence of packets received by a Networking server are not correctly checked.

An attacker could exploit this vulnerability to send specially crafted messages to force the application to stop.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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


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

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

## Is CVE-2025-9998 being exploited?

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

Public exploit code:

- vulnerability in CVE 2025-9998 and solution for those vulnerability with help artificial intelligence (github_poc): https://github.com/balajigund/Research-on-CVE-2025-9998

## Fix prompt for AI coding agents

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

What it is: CVE-2025-9998 is a medium-severity denial of service vulnerability in arcinfo PcVue, published on 5 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-9998 in the wild and no public exploit code.

Affected product: arcinfo PcVue. 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-9998/ (Markdown: https://insights.sbomify.com/CVE-2025-9998/index.md)
```

## Sources

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

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