# CVE-2026-71641: Denial of service in n/a

> An attacker can cause a denial of service in the EGO-Planner-v2 navigation system by exploiting interactions between trajectory server and emergency recovery logic.

- **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:** 11 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-qpcv-7q48-ccxp

## What is CVE-2026-71641?

CVE-2026-71641 is a high-severity denial of service vulnerability in n/a, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in ZJU-FAST-Lab EGO-Planner-v2 All versions up to commit 5c99a95880401e2599638d567abc0e240396cb42 allows an attacker to cause a denial of service via thenteraction between traj_server, poscmd_2_odom, and the EGOReplanFSM emergency recovery logic

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-71641 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71641 is a high-severity denial of service vulnerability in n/a, published on 11 Sep 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-2026-71641 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-2026-71641/ (Markdown: https://insights.sbomify.com/CVE-2026-71641/index.md)
```

## Sources

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

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