# CVE-2025-64388: Denial of service through specific packets

> Attackers can cause a denial of service on the Circutor TCPRS1plus web server by sending specific malicious requests.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-2cfx-ppj7-2856

## What is CVE-2025-64388?

CVE-2025-64388 is a critical denial of service vulnerability in Circutor TCPRS1plus, published on 31 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Denial of service of the web server through specific requests to this protocol

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2025-64388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64388 is a critical denial of service vulnerability in Circutor TCPRS1plus, published on 31 Oct 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-64388 in the wild and no public exploit code.

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

## Sources

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

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