CVE-2026-27152: DIscourse has DM communication-preference bypass when adding members

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, DM communication-preference bypass when adding members via Chat::AddUsersToChannel — a user could add targets who have blocked/ignored/muted them to an existing DM channel, bypassing per-recipient PM restrictions that are enforced during DM channel creation. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. No known workarounds are available.

Affected Software

4 affected components
Discourse<2025.12.2, <2026.1.1, <2026.2.0
Discourse Discourse<2025.12.2
Discourse Discourse>=2026.1.0<2026.1.1
Discourse Discourse=2026.2.0

Event History

Feb 26, 2026
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
DescriptionWeakness
Data Sourced
via NVD·09:28 PM
DescriptionSeverityWeaknessAffected Software
Jun 28, 58142
Event
via FIRST·03:22 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-27152?

CVE-2026-27152 is classified as a medium-severity vulnerability due to the potential for unauthorized DM channel access.

2

How do I fix CVE-2026-27152?

To fix CVE-2026-27152, upgrade to Discourse versions 2025.12.2, 2026.1.1, or 2026.2.0.

3

What vulnerable software versions are affected by CVE-2026-27152?

Discourse versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 are affected by CVE-2026-27152.

4

What specific issue does CVE-2026-27152 address?

CVE-2026-27152 addresses a DM communication-preference bypass that allows users to add blocked contacts to DM channels.

5

Is user data at risk due to CVE-2026-27152?

Yes, user data may be at risk as this vulnerability could allow blocked users to access previously restricted DM channels.

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