Read the docs

Topic publishing in Discourse exposes restricted topics to the public

Priority LOW 39Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · GHSA-6rw5-7wfj-29mw. Fix status from GitHub.

Summary

Discourse lets some non-staff users publish topics they can only read. Publishing moves the topic to another category, relists it, resets its dates and permanently deletes the opening post's edit history. An attacker with low privileges over the network can move a topic from a read-restricted category into a public category, where anyone can read it. Affected users are members of groups allowed to create shared drafts or set topic timers, which by default includes trust level 4.

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

Description from the GitHub advisory

### Impact Publishing a topic moves it to another category, relists it, resets its dates and permanently deletes the opening post's edit history. Some non-staff users could publish topics they were not allowed to edit: - On sites that add non-staff groups to `shared_drafts_allowed_groups`, a member of such a group could publish any topic they could read, not only shared drafts. A member who could edit a topic could also turn it into a shared draft, which hid it from everyone outside the group. - Users allowed to set topic timers, which by default includes trust level 4 users, could schedule a topic they could only read to be published into another category. In both cases, a topic from a read-restricted category could be moved into a public category and become readable by anyone. ### Workarounds Remove non-staff groups from the `shared_drafts_allowed_groups` site setting, and remove trust level 4 from the `topic_timers_allowed_groups` site setting. <!-- patch-triage-lifecycle:7caf7e69f8fece8381d80a21e0756912f5ccdca32f17f69858f28c2143283bb2 -->

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-6rw5-7wfj-29mw
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-6rw5-7wfj-29mw
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-6rw5-7wfj-29mw
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-6rw5-7wfj-29mw
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-6rw5-7wfj-29mw
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-6rw5-7wfj-29mw
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-6rw5-7wfj-29mw
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-6rw5-7wfj-29mw

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. Until then, remove non-staff groups from the shared_drafts_allowed_groups site setting and remove trust level 4 from the topic_timers_allowed_groups site setting.

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

  • Fix · GHSA-6rw5-7wfj-29mw Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-6rw5-7wfj-29mw Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-6rw5-7wfj-29mw Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-6rw5-7wfj-29mw Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-6rw5-7wfj-29mw

References

Sources

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