Vulnerability in discourse (CVE-2026-33514)
Summary
Vulnerability in discourse (CVE-2026-33514). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2026.1.4, 2026.3.1, 2026.4.1 or later.
Original description
The description as published by the source.
Discourse is an open-source discussion platform. In versions prior to 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0, an authenticated user on a Discourse instance with the form templates feature enabled can read the name and structured content of form templates that are intended exclusively for categories they are not authorized to access. Impact is limited to disclosure of site configuration metadata. This issue has been fixed in versions 2026.1.4, 2026.3.1, 2026.4.1 and 2026.5.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33514 has been found in discourse.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade discourse to 2026.1.4, 2026.3.1, 2026.4.1 or later.
If unsure, ask your IT team or search "discourse CVE-2026-33514" on the vendor's site.
CVE-2026-33514 (discourse) — CWE-862 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.1.4, 2026.3.1, 2026.4.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in discourse.
Check the vendor advisory for the affected versions of discourse.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2026.1.4, 2026.3.1, 2026.4.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'discourse' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'discourse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
discourseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade discourse to 2026.1.4, 2026.3.1, 2026.4.1ステージング環境で 2026.1.4, 2026.3.1, 2026.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- patch github.com
- web nvd.nist.gov