CVE-2026-26207: DIscourse's discourse-policy plugin lacks post access check

Published Feb 26, 2026
·
Updated

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, discourse-policy plugin allows any authenticated user to interact with policies on posts they do not have permission to view. The PolicyController loads posts by ID without verifying the current user's access, enabling policy group members to accept/unaccept policies on posts in private categories or PMs they cannot see and any authenticated user to enumerate which post IDs have policies attached via differentiated error responses (information disclosure). The issue is patched in versions 2025.12.2, 2026.1.1, and 2026.2.0 by adding a guardian.cansee?(@post) check in the setpost beforeaction, ensuring post visibility is verified before any policy action is processed. As a workaround, disabling the discourse-policy plugin (policyenabled = false) eliminates the vulnerability. There is no other workaround without upgrading.

Affected Software

4 affected components
discourse/discourse-policy<2025.12.2, <2026.1.1, <2026.2.0
Discourse Discourse<2025.12.0
Discourse Discourse>=2026.1.0<2026.1.1
Discourse Discourse=2026.2.0

Event History

Feb 26, 2026
CVE Published
via MITRE·03:04 PM
Data Sourced
via MITRE·03:04 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:24 PM
DescriptionSeverityWeaknessAffected Software
Oct 1, 58139
Event
via FIRST·09:38 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-26207?

CVE-2026-26207 is classified as a moderate severity vulnerability that affects the Discourse platform.

2

How do I fix CVE-2026-26207?

To fix CVE-2026-26207, upgrade the `discourse-policy` plugin to versions 2025.12.2, 2026.1.1, or 2026.2.0.

3

Who is affected by CVE-2026-26207?

Any authenticated user in Discourse can be affected by CVE-2026-26207 if they interact with posts they do not have permission to view.

4

What is the impact of CVE-2026-26207?

The impact of CVE-2026-26207 allows unauthorized access and manipulation of post policies in Discourse.

5

Is there a workaround for CVE-2026-26207?

There is no official workaround for CVE-2026-26207; the only remedy is to update the affected plugin to a secure version.

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