CVE-2026-55674: Discourse: Cache poisoning/XSS via color scheme cookies
Discourse is an open-source discussion platform. Prior to 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0, an unauthenticated attacker could send a single request with a crafted color_scheme_id (or dark_scheme_id) cookie to inject arbitrary HTML into a Discourse page. Because the cookie value was rendered into a color scheme tag without escaping, the attacker could break out of the attribute and inject a tag that bypassed Discourse's nonce-based Content Security Policy, resulting in arbitrary JavaScript execution in visitors' browsers. This issue is fixed in versions 2026.1.6, 2026.5.2, 2026.6.1, and 2026.7.0.
Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker can make a vulnerable Discourse site generate a poisoned page that runs attacker-controlled JavaScript in visitors’ browsers. This could expose user information or allow actions within a victim’s session. The flaw is remotely reachable but requires a visitor to receive the affected page.
Executive priority
Treat this as an emergency internet-facing application update. The combination of unauthenticated reachability, low complexity, cache-related visitor impact, and browser code execution creates substantial confidentiality and integrity risk. Accelerate upgrades for public forums, then verify clustered nodes and caches consistently serve remediated code.
Technical view
Unescaped color_scheme_id or dark_scheme_id cookie values are inserted into a color-scheme tag. An attacker can escape the HTML attribute and inject markup that bypasses Discourse’s nonce-based Content Security Policy, producing arbitrary JavaScript execution. The CVSS 3.1 score is 9.3, reflecting network reachability, low attack complexity, no privileges, required user interaction, and cross-scope impact.
Likely exposure
Internet-accessible Discourse deployments running versions below 2026.1.6, 2026.5.0-latest through 2026.5.1, or 2026.6.0-latest are exposed. The description also identifies 2026.7.0 as a fixed release. Exact exposure should be confirmed against the deployed release channel and vendor advisory.
Exploitation context
The source states that one crafted unauthenticated request can trigger the flaw, while execution occurs when visitors receive the affected page. CVE-2026-55674 is not listed as KEV in the supplied bundle, and the provided sources do not establish active exploitation.
Researcher notes
The vulnerability is CWE-79 caused by unsafe cookie-to-HTML rendering. Its notable control bypass is injection of a tag accepted by the nonce-based CSP, so CSP presence alone does not remove exposure. The supplied material does not quantify cache duration, affected cache configurations, observed attacks, or indicators of compromise.
Mitigation direction
Upgrade Discourse to 2026.1.6, 2026.5.2, 2026.6.1, 2026.7.0, or a later supported release.
Prioritize public or externally reachable forums because exploitation requires no authenticated account.
Review the vendor advisory for release-channel-specific upgrade guidance.
Clear relevant application and intermediary caches after upgrading to remove potentially poisoned responses.
Validation and detection
Inventory every Discourse instance and record its exact deployed version and release channel.
Confirm each instance meets or exceeds the applicable fixed version.
Verify upgrades completed successfully and all serving nodes run the remediated build.
Review application, proxy, and cache logs for unusual color-scheme cookie activity.
Confirm cached pages were refreshed after remediation.
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-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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.
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
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation
Improper Neutralization of Input During Web Page Generation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.