# CVE-2026-44425: ShellHub: Crash-DoS via field injection in filter and sort-by parameters

> Authenticated users can crash the ShellHub API by injecting malicious keys into filter and sort parameters, causing a denial of service.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-47r2-v3x6-wff9, GO-2026-5113

## What is CVE-2026-44425?

CVE-2026-44425 is a medium-severity denial of service vulnerability in shellhub-io shellhub, published on 13 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ShellHub is a centralized SSH gateway. Prior to 0.24.2, the device list endpoint accepts user-controlled identifiers in the the name field of each filter property in the base64-encoded filter query parameter and the sort_by query parameter, which are then passed directly as BSON/SQL keys in the database layer without validation. Any authenticated user can craft payloads that cause the aggregation / query to fail and the API to return HTTP 500 with no body, with no rate limiting applied. This vulnerability is fixed in 0.24.2.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic), CWE-20 (Improper Input Validation), CWE-1333 (Inefficient Regular Expression Complexity)

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

3 open source packages ship an affected version, including github.com/shellhub-io/shellhub. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |
| `github.com/shellhub-io/shellhub` | Go | All versions | 0.24.2 |

Products: Shellhub Shellhub.

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

Upgrade github.com/shellhub-io/shellhub to 0.24.2 or later.

## Is CVE-2026-44425 being exploited?

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

## Other vulnerabilities in shellhub-io shellhub

- [CVE-2026-44423](https://insights.sbomify.com/CVE-2026-44423/): ShellHub: Cross-tenant IDOR in `GET /api/sessions/:uid` discloses SSH session data (medium 6.5)
- [CVE-2026-44424](https://insights.sbomify.com/CVE-2026-44424/): ShellHub: Cross-tenant IDOR in `GET /api/devices/:uid` discloses device data of any namespace (medium 6.5)
- [CVE-2026-44426](https://insights.sbomify.com/CVE-2026-44426/): ShellHub: Cross-tenant IDOR in `GET /api/namespaces/:tenant` via API Key bypasses membership check (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44425 is a medium-severity denial of service vulnerability in shellhub-io shellhub, published on 13 May 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-44425 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2
- github.com/shellhub-io/shellhub (Go): affected all versions; fixed in 0.24.2

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-44425/ (Markdown: https://insights.sbomify.com/CVE-2026-44425/index.md)
```

## Sources

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

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