Read the docs

Moving posts can leak topic titles in Discourse

Priority LOW 35Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · GHSA-5hwp-4jcj-w85x. Fix status from GitHub.

Summary

Discourse is affected in all versions. When posts are moved into a topic in a read-restricted category, the notice left in the original topic reveals the destination topic's title and a link to it. Any user who can read the original topic, including anonymous visitors of a public topic, can learn the title of a topic they are not allowed to see. The disclosure happens as a side effect when a staff member or a user with permission to move posts moves them.

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

Description from the GitHub advisory

### Impact When posts were moved into a topic in a read-restricted category, either by merging them into an existing topic or by splitting them into a new one, the notice left in the original topic included the destination topic's title and a link containing its slug and ID. Any user able to read the original topic, including anonymous visitors when that topic is public, could learn the title of a topic they are not allowed to see. Moving posts requires a staff member or a user with permission to move posts, so the disclosure only happens as a side effect of their action. The contents of the destination topic are not exposed. All versions of Discourse are affected; the notice has included the destination title since posts could first be moved. The fix omits the destination title and link from the notice unless every user who can read the original topic can also read the destination. Notices created before upgrading are not changed. ### Workarounds Avoid moving posts from less restricted topics into topics in read-restricted categories. Existing move notices that reference restricted topics can be deleted by staff. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-XI1ORQA2.

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-5hwp-4jcj-w85x
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-5hwp-4jcj-w85x
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-5hwp-4jcj-w85x
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-5hwp-4jcj-w85x
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-5hwp-4jcj-w85x
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-5hwp-4jcj-w85x
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-5hwp-4jcj-w85x
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-5hwp-4jcj-w85x

Remediation

Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, matching the release line in use. Notices created before upgrading are not changed, so staff can delete existing move notices that reference restricted topics.

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

  • Fix · GHSA-5hwp-4jcj-w85x Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-5hwp-4jcj-w85x Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-5hwp-4jcj-w85x Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-5hwp-4jcj-w85x Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-5hwp-4jcj-w85x

References

Sources

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