Vulnerability from bitnami_vulndb
Published
2026-03-27 07:11
Modified
2026-03-27 07:40
Summary
Discourse hardens chat DM channel creation and expansion
Details

Discourse is an open-source discussion platform. Versions prior to 2026.3.0, 2026.2.1, and 2026.1.2 have two authorization issues in the chat direct message API. First, when creating a direct message channel or adding users to an existing one, the target_groups parameter was passed directly to the user resolution query without checking group or member visibility for the acting user. An authenticated chat user could craft an API request with a known private/hidden group name and receive a channel containing that group's members, leaking their identities. Second, can_chat? only checked group membership, not the chat_enabled user preference. A chat-disabled user could create or query DM channels between other users via the direct messages API, potentially exposing private last_message content from the serialized channel response. Versions 2026.3.0, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.


{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "discourse",
        "purl": "pkg:bitnami/discourse"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2026.1.0"
            },
            {
              "fixed": "2026.1.2"
            },
            {
              "introduced": "2026.2.0"
            },
            {
              "fixed": "2026.2.1"
            },
            {
              "introduced": "2026.3.0"
            },
            {
              "fixed": "2026.3.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-33410"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:discourse:discourse:*:*:*:*:*:*:*:*"
    ],
    "severity": "Medium"
  },
  "details": "Discourse is an open-source discussion platform. Versions prior to 2026.3.0, 2026.2.1, and 2026.1.2 have two authorization issues in the chat direct message API. First, when creating a direct message channel or adding users to an existing one, the `target_groups` parameter was passed directly to the user resolution query without checking group or member visibility for the acting user. An authenticated chat user could craft an API request with a known private/hidden group name and receive a channel containing that group\u0027s members, leaking their identities. Second, `can_chat?` only checked group membership, not the `chat_enabled` user preference. A chat-disabled user could create or query DM channels between other users via the direct messages API, potentially exposing private `last_message` content from the serialized channel response. Versions 2026.3.0, 2026.2.1, and 2026.1.2 contain a patch. No known workarounds are available.",
  "id": "BIT-discourse-2026-33410",
  "modified": "2026-03-27T07:40:55.991Z",
  "published": "2026-03-27T07:11:02.112Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/discourse/discourse/security/advisories/GHSA-2m5j-6v2r-cq2h"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33410"
    }
  ],
  "schema_version": "1.6.2",
  "summary": "Discourse hardens chat DM channel creation and expansion"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…