# CVE-2026-89201: SQL injection in RUGGEDCOM CROSSBOW

> An authenticated attacker can execute arbitrary SQL commands via unsanitized input in device group or facility names during Bulk Export.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-84qj-482m-vxjx

## What is CVE-2026-89201?

CVE-2026-89201 is a high-severity SQL injection vulnerability in Siemens RUGGEDCOM CROSSBOW, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V6.0). Affected devices do not properly validate or sanitize input in device group or facility names processed during the Bulk Export workflow. This could allow an authenticated attacker with specific privileges to execute arbitrary SQL commands on the underlying database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

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

## Is CVE-2026-89201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89201 is a high-severity SQL injection vulnerability in Siemens RUGGEDCOM CROSSBOW, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89201 in the wild and no public exploit code.

Affected product: Siemens RUGGEDCOM CROSSBOW. 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-89201/ (Markdown: https://insights.sbomify.com/CVE-2026-89201/index.md)
```

## Sources

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

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