CVE-2026-84302: Discourse: Non-participant moderators can read, edit, and delete PM content through Discourse AI reviewables

Published Sep 24, 2026
·
Updated

Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, Discourse AI reviewables associated with private messages could appear in the moderator review queue of a moderator who was not a participant in the message. Reviewable visibility filtering did not restrict private-message reviewables to the audience permitted to access the underlying private-message topic, allowing the moderator to read otherwise confidential content. Depending on the available reviewable action, the moderator could also modify the private message by closing its topic or deleting a post. Exploitation requires an authenticated moderator account and a pre-existing Discourse AI reviewable associated with a private message. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.

Affected Software

1 affected component
Discourse Discourse<2026.1.6, <2026.5.2, <2026.6.1, <2026.7.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.1.6
  2. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.5.2
  3. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.6.1
  4. Upgrade

    Upgrade Discourse to a version that resolves this vulnerability.

    Fixed in 2026.7.0

Event History

Sep 24, 2026
CVE Published
via MITRE·04:49 PM
Data Sourced
via MITRE·04:49 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

Discourse deployments running versions earlier than 2026.1.6, 2026.5.2, 2026.6.1, or 2026.7.0 are affected. The issue concerns private messages that have an associated Discourse AI reviewable.

2

What access and conditions are required to exploit this issue?

An attacker needs an authenticated moderator account and a pre-existing Discourse AI reviewable tied to a private message. The moderator does not need to be a participant in that private-message conversation.

3

What could an unauthorized moderator do?

They could view confidential private-message content through the moderator review queue. Depending on the available reviewable action, they could also close the private-message topic or delete a post.

4

How can the issue be remediated?

Upgrade Discourse to version 2026.1.6, 2026.5.2, 2026.6.1, or 2026.7.0. These versions contain the fix for private-message reviewable visibility filtering.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203