CVE-2026-55674: Discourse · Cache poisoning/XSS via color scheme cookies
Affects discourseSource GCVE Database
Not known to be exploited · fixed in 2026.6.1 : patch discourse as a priority.
Data as of 20 Nov 2026, 17:35 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.6.1, 2026.5.2, 2026.1.6
Exploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade discourse to 2026.6.1, 2026.5.2 or 2026.1.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamidiscoursepkg:bitnami/discourseOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official patches by upgrading Discourse to version 2026.1.6, 2026.5.2, 2026.6.1, or later versions such as 2026.7.0. These versions contain fixes that properly escape cookie values to prevent injection and bypass of the Content Security Policy. No other mitigation is indicated by the vendor advisory.
Description
Discourse versions prior to 2026.1.6, 2026.5.2, and 2026.6.1 contain a vulnerability where an unauthenticated attacker can inject arbitrary HTML via crafted color_scheme_id or dark_scheme_id cookies. This injection bypasses the platform's nonce-based Content Security Policy, enabling arbitrary JavaScript execution in visitors' browsers. The issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.