CVE-2026-33251 json
Discourse has a Hidden Solved topics permission bypass
published 7mo ago modified 2mo ago also BIT-discourse-2026-33251 , EUVD-2026-13895 , GHSA-vm2x-9h8x-7jxm
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
Discourse is an open-source discussion platform. Prior to versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2, an authorization bypass vulnerability in hidden Solved topics may allow unauthorized users to accept or unaccept solutions. Versions 2026.3.0-latest.1, 2026.2.1, and 2026.1.2 contain a patch. As a workaround, ensure only trusted users are part of the Site Setting for accept_all_solutions_allowed_groups.
Patch / fix
- bitnami discourse 2026.1.2, 2026.2.1, 2026.3.0
- discourse discourse 2026.1.2, 2026.2.1
Is CVE-2026-33251 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
| OSV | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | discourse | >=2026.1.0, <2026.1.2 >=2026.2.0, <2026.2.1 >=2026.3.0, <2026.3.0 |
2026.1.2 2026.2.1 2026.3.0 |
Affected products
- discourse discourse
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
References
-
github.com
/discourse/discourse/security/advisories/GHSA-vm2x-9h8x-7jxm
mitigation, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-33251
web
Sources
- CVE List CVE-2026-33251
- NVD CVE-2026-33251
- OSV BIT-discourse-2026-33251
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.