Cyber Resilience

CVE-2026-28227

Access Control in Discourse ≤ 2025.12.2

Published
26 February 2026
Modified
02 March 2026
Patch / advisory
CVSS Score v4 1.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.028 85th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-28227 is a low-severity Incorrect Authorization (CWE-863) vulnerability in Discourse Discourse. Its CVSS base score is 1.2 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 15% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, TL4 users can publish topics into staff-only categories via the `publish_to_category` topic timer, bypassing authorization checks. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. No known…

more

workarounds are available.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Why these techniques?

Auth bypass in public-facing Discourse app directly enables privilege escalation (T1068) via exploitation of web application (T1190).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-68933Same product: Discourse Discourse
CVE-2026-28282Same product: Discourse Discourse
CVE-2026-33428Same product: Discourse Discourse
CVE-2026-33251Same product: Discourse Discourse
CVE-2026-33424Same product: Discourse Discourse
CVE-2026-27936Same product: Discourse Discourse
CVE-2025-69289Same product: Discourse Discourse
CVE-2025-69218Same product: Discourse Discourse
CVE-2025-68666Same product: Discourse Discourse
CVE-2023-32061Same product: Discourse Discourse

Affected Assets

discourse
discourse
2026.2.0 · ≤ 2025.12.2 · 2026.1.0 — 2026.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-6 Least Privilege
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization policy on topic publication actions, blocking TL4 users from writing into staff-only categories via publish_to_category timers.

prevent

Ensures TL4 users receive only the minimum privileges required, preventing assignment of rights that would allow access to staff categories even through timer features.

prevent

Enforces information flow rules between topic categories, stopping unauthorized movement of content into restricted staff areas.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Defining, enforcing, and reviewing access authorizations and least privilege directly prevents incorrect authorization checks.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Requiring consistency between access rights and classification plus formal approval steps ensures that the authorization logic correctly distinguishes between entities that should and should not be granted access.

prevents

Enforcing policy-driven approval and role-change reviews stops incorrect or stale authorization decisions from remaining in effect after job changes or terminations.

prevents

By tying access rights to identity, device, location and classification, the control reduces the likelihood that an authorization decision will be based on an incorrect or bypassed policy.

References