# CVE-2026-71644: Business logic in n/a

> Attackers can cause unsafe trajectory planning and potential UAV collisions by exploiting a missing default case in the swarm FSM.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 11 Sep 2026
- **Also known as:** GHSA-jh98-9grg-5fp6

## What is CVE-2026-71644?

CVE-2026-71644 is a critical 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 Robotics-STAR-Lab (SYSU STAR Group) RACER Tested affected version: commit abcdef1234567890 allows an attacker to cause unsafe trajectory planning and potential UAV collisions via a missing default case in the FSM that stops publishing swarm trajectories when the drone enters IDLE

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

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

## Is CVE-2026-71644 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-71644 is a critical 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-71644 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-71644/ (Markdown: https://insights.sbomify.com/CVE-2026-71644/index.md)
```

## Sources

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

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