Read the docs

Discourse automation trigger leaks private post excerpts

Priority LOW 27Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-478q-976m-pm7g. Fix status from GitHub.

Summary

Discourse from 2026.7.0-latest before 2026.7.5, from 2026.9.0-latest before 2026.9.2 and from 2026.10.0-latest before 2026.10.1 are affected. The automation trigger endpoint accepts forged event context, so an attacker can make an automation process data about private posts and disclose post excerpts to unauthorized recipients. The attacker needs an administrator API key scoped to automation:trigger_automation, the automation ID and a valid action ID that references a private post. The CVSS 3.1 severity is low and only confidentiality is affected.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact A vulnerability exists in the automation trigger endpoint (`POST /automations/:id/trigger.json`) that could allow disclosure of private post content. An attacker with a granular API key scoped only to `automation:trigger_automation` could invoke automations that are configured for event-only triggering (such as the flagged-post email notification workflow). By supplying forged event context, the attacker could cause the automation to process data referencing private posts, potentially leading to disclosure of post excerpts to unauthorized recipients. The issue is limited by several preconditions: the attacker must possess a valid API key bound to an administrator account with the `automation:trigger_automation` scope, know the automation ID, and be able to supply a valid action ID referencing a private post. The granular key alone does not provide direct access to private topics or posts. Only confidentiality is affected; there is no impact on data integrity (no posts or topics are modified) or availability. ### Workarounds No known workarounds for this issue. <!-- patch-triage-lifecycle:0c42bb79579ede228fd909e86e34bd5f82cc0745d4ca402c93dfd46c08f6d3d3 -->

Why it matters now

Fix Fixed Discourse: 2026.11.0-latest.1, 2026.10.1, 2026.9.2 +1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.11.0-latest.1Patch availableGHSA-478q-976m-pm7g
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-478q-976m-pm7g
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-478q-976m-pm7g
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-478q-976m-pm7g
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-478q-976m-pm7g
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-478q-976m-pm7g
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-478q-976m-pm7g
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-478q-976m-pm7g

Remediation

Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, depending on the release line in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-478q-976m-pm7g Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-478q-976m-pm7g Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-478q-976m-pm7g Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-478q-976m-pm7g Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-478q-976m-pm7g

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences