# CVE-2026-75937: OS Command Injection in Digi Accelerated Linux (DAL OS)

> Unauthenticated attackers can execute arbitrary OS commands with root privileges via HTTP POST requests to the web interface of Digi devices.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 2 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-qqmh-gh5m-j2h2

## What is CVE-2026-75937?

CVE-2026-75937 is a critical command injection vulnerability in Digi International AnywhereUSB Plus Family, published on 2 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A specially crafted HTTP POST request to the web administration interface allows an unauthenticated attacker to execute arbitrary operating system commands with root privileges on the affected device. Disable the web server when not configuring the device.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-75937 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75937 is a critical command injection vulnerability in Digi International AnywhereUSB Plus Family, published on 2 Oct 2026. 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-2026-75937 in the wild and no public exploit code.

Affected product: Digi International AnywhereUSB Plus Family. 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-75937/ (Markdown: https://insights.sbomify.com/CVE-2026-75937/index.md)
```

## Sources

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

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