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.
CVE-2026-55674
This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.3
- EG Score
- 9.3(medium)
- EG Risk
- 42(Track)EG Risk 42/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity93% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 28%
- KEV
- Not listed
Published
August 17, 2026
Last Modified
August 18, 2026
Advisory Details (1)
Auto-updated Aug 23, 2026Cache poisoning/XSS via color scheme cookies · Advisory · discourse/discourse · GitHub
https://github.com/discourse/discourse/security/advisories/GHSA-qx4v-rg4v-pm2gWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 03:10 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 05:38 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 15:44 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 16:26 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 17:06 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 17:55 UTCEG score recompute
- 2026-08-24 10:14 UTCEG score recompute
- 2026-08-23 03:25 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 00:33 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:32 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 18:25 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:25 UTCEG score recompute
- 2026-08-18 14:51 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 16:22 UTCEG score recompute
- 2026-08-17 16:10 UTCEG score recompute
Show 1 moreShow fewer
- 2026-08-17 16:09 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55674?
When was CVE-2026-55674 disclosed?
Is CVE-2026-55674 actively exploited?
What is the CVSS score of CVE-2026-55674?
How do I remediate CVE-2026-55674?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55674
Is Your Infrastructure Affected by CVE-2026-55674?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.