Hidden post content exposed in Discourse feeds, metadata and emails
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-h2q4-93mj-v5xr. Fix status from GitHub.
Summary
Discourse versions 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. Hidden posts can leak to people who may not view them through the topic RSS feed, topic metadata and digest emails. An anonymous visitor with a topic URL can read the raw body of a hidden first post, and the flaw does not allow modifying posts or escalating privileges.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact Posts hidden by community flags or staff action could be disclosed to people who were not permitted to view them. An anonymous visitor with a topic URL could read the full raw body of a hidden first post in the topic RSS feed’s channel description. The topic’s HTML description and Open Graph and Twitter metadata could also expose excerpts from a hidden first or requested post, including when a visitor requested a visible reply. Separately, digest emails could include an excerpt from a hidden reply selected as the topic’s highest-scored post. In a default configuration, hidden posts are visible to their authors, staff, and trust level 4 users. This issue allowed anonymous visitors and ordinary users to obtain content they should not have been able to read. It did not allow modification of posts or escalation of privileges ### Workarounds No known complete workaround is available. Updating to a fixed version is recommended.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | Discourse | — | 2026.11.0-latest.1 | Patch available | GHSA-h2q4-93mj-v5xr |
| — | Discourse | >= 2026.10.0-latest | 2026.10.1 | Patch available | GHSA-h2q4-93mj-v5xr |
| — | Discourse | >= 2026.9.0-latest | 2026.9.2 | Patch available | GHSA-h2q4-93mj-v5xr |
| — | Discourse | >= 2026.7.0-latest | 2026.7.5 | Patch available | GHSA-h2q4-93mj-v5xr |
- Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-h2q4-93mj-v5xr
- Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-h2q4-93mj-v5xr
- Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-h2q4-93mj-v5xr
- Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-h2q4-93mj-v5xr
Remediation
Update Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, depending on the release line. No known complete workaround is available.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-h2q4-93mj-v5xr Discourse Fixed in 2026.11.0-latest.1 Advisory →
- Fix · GHSA-h2q4-93mj-v5xr Discourse Fixed in 2026.10.1 Advisory →
- Fix · GHSA-h2q4-93mj-v5xr Discourse Fixed in 2026.9.2 Advisory →
- Fix · GHSA-h2q4-93mj-v5xr Discourse Fixed in 2026.7.5 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-h2q4-93mj-v5xr
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences