<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 01:07:47 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-44425</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-44425</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-44425</guid>
    </item>
    <item>
      <title>GHSA-47r2-v3x6-wff9 — ShellHub has crash-DoS via field injection in filter and sort-by parameters</title>
      <link>https://db.gcve.eu/vuln/ghsa-47r2-v3x6-wff9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/shellhub-io/shellhub&lt;/p&gt;
&lt;p&gt;## 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:&lt;/p&gt;
&lt;p&gt;1. The `name` field of each filter property in the base64-encoded `filter`
     query parameter.
  2. The `sort_by` query parameter.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Severity
**CVSS 3.1: 6.5 (Medium)** 
CWE-20 (Improper Input Validation) 
CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)&lt;/p&gt;
&lt;p&gt;## Affected versions
ShellHub Community v0.24.1 (validated). All versions sharing the same filter and sort pipeline (`api/store/mongo/query-options.go`).&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;### Vector 1 — Filter field name
  `api/store/mongo/query-options.go:140`:&lt;/p&gt;
&lt;p&gt;```go
  conditions = append(conditions, bson.M{param.Name: property})
  ```&lt;/p&gt;
&lt;p&gt;`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 virtual pipeline-computed fields (`namespace`, paths containing `$`) to be  injected.&lt;/p&gt;
&lt;p&gt;### Vector 2 — Sort-by field
Similar pattern in the sort pipeline where the `sort_by` query parameter is used to build `bson.M{&amp;#34;$sort&amp;#34;: {sortBy: order}}` without validation.&lt;/p&gt;
&lt;p&gt;### Additional observation
`fromContains` (`api/store/mongo/internal/filters.go:60-69`) passes user in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/shellhub-io/shellhub&lt;/p&gt;
&lt;p&gt;## 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:&lt;/p&gt;
&lt;p&gt;1. The `name` field of each filter property in the base64-encoded `filter`
     query parameter.
  2. The `sort_by` query parameter.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Severity
**CVSS 3.1: 6.5 (Medium)** 
CWE-20 (Improper Input Validation) 
CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)&lt;/p&gt;
&lt;p&gt;## Affected versions
ShellHub Community v0.24.1 (validated). All versions sharing the same filter and sort pipeline (`api/store/mongo/query-options.go`).&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;### Vector 1 — Filter field name
  `api/store/mongo/query-options.go:140`:&lt;/p&gt;
&lt;p&gt;```go
  conditions = append(conditions, bson.M{param.Name: property})
  ```&lt;/p&gt;
&lt;p&gt;`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 virtual pipeline-computed fields (`namespace`, paths containing `$`) to be  injected.&lt;/p&gt;
&lt;p&gt;### Vector 2 — Sort-by field
Similar pattern in the sort pipeline where the `sort_by` query parameter is used to build `bson.M{&amp;#34;$sort&amp;#34;: {sortBy: order}}` without validation.&lt;/p&gt;
&lt;p&gt;### Additional observation
`fromContains` (`api/store/mongo/internal/filters.go:60-69`) passes user in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-47r2-v3x6-wff9</guid>
    </item>
  </channel>
</rss>
