CVE-2026-27934
Information Disclosure via User Action API in Discourse
Publication date: 2026-03-19
Last updated on: 2026-03-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| discourse | discourse | From 2026.1.0 (inc) to 2026.1.2 (exc) |
| discourse | discourse | From 2026.2.0 (inc) to 2026.2.1 (exc) |
| discourse | discourse | 2026.3.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-201 | The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized disclosure of information, specifically the titles and excerpts of posts on the Discourse platform. This means that sensitive or private discussion content could be exposed to users who should not have access, potentially compromising confidentiality.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
Can you explain this vulnerability to me?
This vulnerability affects Discourse, an open-source discussion platform. In versions prior to 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, there is a lack of visibility checks in a user action API endpoint. This flaw allows unauthorized users to access the title and post excerpt of discussions, leading to unintended information disclosure.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Discourse to one of the patched versions: 2026.3.0-latest.1, 2026.2.1, or 2026.1.2.
No known workarounds are available, so applying the patch by upgrading is the immediate recommended step.