LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26979: Discourse: TL4 users are able to change status of restricted topics

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, TL4 users are able to close, archive and pin topics in private categories they don't have access to. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. No known workarounds are available.

NoneCVSS 0Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-26979 affects Discourse. Highly trusted TL4 users could close, archive, or pin topics inside private categories they cannot access. This does not indicate they can read restricted content, but they could disrupt visibility or workflow for private discussions. Patched Discourse versions are available.

Executive priority

Treat as a routine but timely platform update. The issue is not presented as data theft or active exploitation, but it can undermine private community moderation controls. Prioritize patching where private categories support sensitive internal, customer, or partner communications.

Technical view

The issue is an authorization flaw, mapped to CWE-862. Before Discourse 2025.12.2, 2026.1.1, and 2026.2.0, TL4 users could change topic status in private categories without category access. The CVSS v4 vector is network-accessible, low complexity, high privileges required, no user interaction, and no scored confidentiality, integrity, or availability impact.

Likely exposure

Exposure is limited to Discourse instances running affected versions where TL4 users exist. The action requires a high-privilege community trust level, reducing broad external risk. Private-category governance and moderation workflows are the main concern.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. The advisory states no known workarounds are available. Abuse would require a TL4 account and would affect restricted-topic status rather than disclose topic contents, based on available information.

Researcher notes

Evidence is limited to the CVE record and Discourse GitHub advisory. The version ranges include stable and latest-track branches. The published CVSS score is 0 despite an authorization bypass description; assess local business impact separately where topic status controls are security-relevant.

Mitigation direction

  • Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later applicable release.
  • If immediate upgrade is delayed, review vendor guidance; no workaround is named in the sources.
  • Review TL4 membership and reduce unnecessary highly trusted accounts until patched.

Validation and detection

  • Identify all Discourse instances and confirm their running version.
  • Check whether versions fall below 2025.12.2, 2026.1.1, or 2026.2.0.
  • Review moderation logs for unusual close, archive, or pin actions on private-category topics.
  • Confirm the GitHub advisory applies to your deployed Discourse branch.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26979 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
None
CVSS
0 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
0CVSS 4.0NoneCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

0None
CVSS 4.0 vector shape for CVE-2026-26979Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
discoursediscourse< 2025.12.2, >= 2026.1.0-latest, < 2026.1.1, >= 2026.2.0-latest, < 2026.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.