Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Discourse MessageBus endpoint
-
ExploitSubscribe to public chat event channel
-
ExecutionReceive unscoped chat payloads in real time
-
ImpactHarvest sensitive message content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Discourse instance is running an affected version (2026.1.0-2026.1.3, 2026.3.0, or 2026.4.0) with the chat feature enabled and at least one public category chat channel in active use; the attacker must be able to reach the MessageBus endpoint over the network and subscribe to the unscoped chat event channel. Limiting factors are that only public-category chat events are exposed (private-category and DM chat are not implicated by the description), the issue only leaks chat traffic generated while the attacker is subscribed (no historical retrieval), and the impact is confidentiality-only with no write or denial-of-service capability. |
| Impact | CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) reflecting network-reachable, unauthenticated read access to chat content with no integrity or availability impact, which is consistent with the description's information-disclosure nature. No EPSS score, KEV listing, or POC was provided, so there is no signal of active exploitation; risk should be treated as opportunistic rather than confirmed in-the-wild abuse. The realistic priority is moderate-to-high for Discourse instances that host sensitive discussions in public-category chat (where 'public' here means category visibility, not necessarily the message content), and lower for forums that do not use the chat plugin. Note that C:H may be generous given that only public-category chat (not DMs or private categories per the description) is exposed - but it remains appropriate because chat content can still be sensitive and is leaked to users explicitly not entitled to receive it. |
| Exploit ScenarioDerived | An attacker registers or uses any account on a Discourse forum that has chat enabled site-wide but disabled for their user, opens a MessageBus long-poll subscription to the public chat event channels, and passively receives chat messages from public category channels in real time as legitimate users send them. Because PR:N and UI:N, an unauthenticated client able to reach MessageBus could likewise subscribe and harvest payloads without any victim interaction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 12, 2026
Information disclosure in Discourse discussion platform allows any MessageBus subscriber to receive real-time chat message payloads from public category channels without proper permission scoping, even when chat is not enabled for that user. The flaw affects versions 2026.1.0 through 2026.1.3, 2026.3.0 through 2026.3.0, and 2026.4.0 through 2026.4.0, and is fixed in 2026.1.4, 2026.3.1, 2026.4.1, and 2026.5.0-latest.1. No public exploit identified at time of analysis, but the unauthenticated network attack vector makes this a meaningful confidentiality concern for forums leveraging chat.
RemediationAI
Vendor-released patch: upgrade Discourse to 2026.1.4, 2026.3.1, 2026.4.1, or 2026.5.0-latest.1 as appropriate for your release train, per advisory https://github.com/discourse/discourse/security/advisories/GHSA-j7wq-rf5c-8783. If patching must be deferred, compensating controls include disabling the chat plugin entirely (eliminates the leak but removes chat functionality for all users), restricting use of public-category chat channels and moving sensitive discussion to private categories or DMs (reduces exposure but does not close the bug for any remaining public channels), or fronting MessageBus endpoints with an authenticating reverse proxy that blocks unauthenticated subscribers (reduces anonymous abuse but does not stop authenticated forum users without chat enabled from subscribing).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Discourse uses MessageBus, a long-polling pub/sub bus, to push real-time updates (notifications, posts, chat events) to subscribed clients. The vulnerability is a CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) caused by chat events for public category channels being published to MessageBus channels without applying the chat-permission scoping that should restrict delivery to users with chat actually enabled. Because MessageBus delivery is based on the channel/topic name a client subscribes to, any subscriber that knows or guesses the public chat event channel receives the payloads. The affected package per CPE is cpe:2.3:a:discourse:discourse on all listed versions in the vulnerable ranges.
Know when Discourse gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Realistic attacker is an authenticated forum user subscribing to MessageBus (PR:L), and only public-category chat content leaks, so confidentiality impact is limited (C:L), with no integrity or availability effect.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
1DescriptionCVE.org
Discourse is an open-source discussion platform. From versions 2026.1.0-latest to before 2026.1.4, 2026.3.0-latest to before 2026.3.1, and 2026.4.0-latest to before 2026.4.1, chat events for public category channels are published to MessageBus without permission scoping, so any MessageBus subscriber without chat enabled could receive chat message payloads in real time. This issue has been patched in versions 2026.1.4, 2026.3.1, 2026.4.1, and 2026.5.0-latest.1.
Executive ViewAI
Discourse discussion platform versions 2026.1.0-2026.4.0 contain an information disclosure vulnerability that allows unauthenticated attackers to intercept real-time chat messages from public category channels. This exposes sensitive organizational communications and user data across community forums, regardless of chat feature configuration. Immediate patching is essential to prevent unauthorized disclosure of confidential discussions.
Apply vendor patch. Patched versions available: 2026.1.4, 2026.3.1, 2026.4.1, 2026.5.0-latest.1. Until patched, restrict real-time chat access to authenticated users only and disable public channel MessageBus subscriptions for unauthenticated connections.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Discourse versions prior to 3.5.0.beta6 contain a reflected cross-site scripting (XSS) vulnerability in social login fun
discourse-bbcode is the official BBCode plugin for Discourse. Rated critical severity (CVSS 9.8), this vulnerability is
Unauthorized information disclosure in Discourse discussion platform versions prior to 2026.3.0-latest.1, 2026.2.1, and
Discourse is an open source platform for community discussion. Rated high severity (CVSS 8.2), this vulnerability is rem
Discourse versions prior to 2025.12.2, 2026.1.1, and 2026.2.0 contain an insecure direct object reference (IDOR) in the
In Discourse 2.7.0 through beta1, a rate-limit bypass leads to a bypass of the 2FA requirement for certain forms. Rated
Unauthenticated attackers can submit forged webhook payloads to multiple email provider integrations in Discourse versio
Discourse is an open-source discussion platform. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploi
Discourse is an open source platform for community discussion. Rated medium severity (CVSS 5.9), this vulnerability is r
Discourse versions prior to 3.4.4 (stable), 3.5.0.beta5 (beta), and 3.5.0.beta6-dev (tests-passed) contain a critical vu
Discourse is an open source platform for community discussion. Rated critical severity (CVSS 9.8), this vulnerability is
Discourse Patreon enables syncronization between Discourse Groups and Patreon rewards. Rated critical severity (CVSS 9.8
EUVD-2026-36582
NVD
CVE.org
EPSS
Vulnrichment
GitHub
Exploit-DB