External risk intelligence

Discourse Cross-Site Scripting via Crafted Cookie

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-55674

Discourse is designed as a public-facing discussion platform. By its nature, the service is intended to be accessible to the internet for user interaction, making its web interface and associated cookies part of a public-facing web application that is reachable by design.

Cross-site Scripting

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A security vulnerability in the Discourse discussion platform could allow an unauthenticated attacker to inject malicious code into pages, leading to arbitrary JavaScript execution in users' browsers. This occurs because a crafted cookie value is not properly handled, bypassing security measures and enabling the execution of unauthorized scripts. The main concern is confirming relevance and exposure due to the platform's public-facing nature.

  • Unauthenticated code injection in discussions.
  • Impacts user browsers via website visits.
  • Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could inject arbitrary HTML and JavaScript into a Discourse platform by sending a specially crafted request containing a malicious cookie. This crafted cookie, specifically the `color_scheme_id` or `dark_scheme_id`, would bypass security measures and execute code within the browser of any visitor viewing the affected page.

  • No authentication required.
  • Crafted cookie injection.
  • Arbitrary JavaScript execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an unauthenticated attacker to inject arbitrary HTML and execute JavaScript in visitors' browsers by sending a crafted request with a malicious cookie. This could occur on any Discourse page when the affected cookie is rendered without proper escaping, potentially bypassing security policies.

  • User browser sessions.
  • Malicious JavaScript injection via cookies.
  • Arbitrary JavaScript execution in browsers.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Discourse platform's administrative or infrastructure teams are likely responsible for managing this vulnerability. The first practical step is to identify all instances of Discourse, determine their internet reachability and business criticality, and then ascertain the accountable owner. Once identified, a remediation plan should be developed based on the assessed risk.

  • Determine asset ownership and exposure.
  • Verify if vulnerable instances are reachable.
  • Plan remediation or risk reduction actions.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Discourse?

Discourse is an open-source platform used to host online discussion forums and community boards. It provides the infrastructure for users to post topics, reply to threads, and engage in real-time communication. Because it is designed to be a public-facing community space, it relies heavily on web browser functionality and cookie-based sessions to manage user preferences and site features.

What is the vulnerability in CVE-2026-55674?

This vulnerability is a type of Cross-Site Scripting, or CWE-79. It occurs because the application fails to properly sanitize or escape data inside specific cookies—specifically those related to color schemes. An attacker can use this flaw to inject their own HTML and malicious JavaScript, which the browser then executes as if it were a legitimate part of the website.

How does an attacker trigger this issue?

An attacker triggers this by sending a web request that includes a specially crafted `color_scheme_id` or `dark_scheme_id` cookie. Simply visiting a page normally does not trigger the bug; the malicious code must be intentionally introduced into the cookie value by the attacker. If the site is running a patched version, the application will correctly handle the cookie and prevent the injected code from executing.

Is my Discourse instance at risk?

According to Halo Surface Signal, Discourse is designed to be a public-facing platform, making it inherently accessible via the internet. Because this flaw affects the way the platform processes cookies from any visitor, any instance that is reachable online is potentially at risk of being used to target your users. Instances that are strictly internal or behind strict access controls may face reduced risk, but patching remains the recommended approach.

How do I secure my installation?

To address this, you should verify your currently installed version of Discourse. If you are running a version prior to 2026.1.6, 2026.5.2, 2026.6.1, or 2026.7.0, you are using a vulnerable release. The primary step is to coordinate an update to one of these patched versions or newer. Begin by identifying all instances of the software within your infrastructure to ensure all community sites are covered by the update.

References