ShellHub has crash-DoS via field injection in filter and sort-by parameters

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

EPSS

• CVE-2026-44425: 0.25% estimated exploitation activity in the next 30 days; percentile 16.83 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The device list endpoint accepts user-controlled identifiers in two places that are passed directly as BSON/SQL keys in the database layer without validation: 1. The name field of each filter property in the base64-encoded filter query parameter. 2. The sortby query parameter. 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. Severity CVSS 3.1: 6.5 (Medium) CWE-20 (Improper Input Validation) CWE-943 (Improper Neutralization of Special Elements in Data Query Logic) Affected versions ShellHub Community v0.24.1 (validated). All versions sharing the same filter and sort pipeline (api/store/mongo/query-options.go). Root cause Vector 1 — Filter field name api/store/mongo/query-options.go:140: param.Name is the name field from the JSON filter supplied by the client. It becomes a BSON map key with no validation, allowing BSON operator names ($where, $ne, $or, $regex) and…

Published by the source

6 May 2026, 23:28 UTC

Last modified by the source

14 May 2026, 20:43 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-47r2-v3x6-wff9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44425

Advisory: ShellHub has crash-DoS via field injection in filter and sort-by parameters
IDs: CVE-2026-44425, GHSA-47r2-v3x6-wff9
Record: https://patchnext.com/advisories/cve-2026-44425 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/shellhub-io/shellhub 0.24.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/shellhub-io/shellhub: affected <= 0.24.1; fixed in 0.24.2

## Suggested inspection (read-only)
- Go github.com/shellhub-io/shellhub: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/shellhub-io/shellhub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-47r2-v3x6-wff9 (GitHub-reviewed advisory GHSA-47r2-v3x6-wff9 lists affected ranges: Go github.com/shellhub-io/shellhub >=0 <=0.24.1)

Commands are suggestions: review each one before running it.