Read the docs

Denial of service via unbounded search terms in Discourse

Priority MEDIUM 48Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-5549-q35w-w4m6. Fix status from GitHub.

Summary

Discourse's full-text search accepts unbounded search terms and passes them directly to the database's ranking functions. An unauthenticated remote attacker can send a crafted search query combined with specific content patterns to consume excessive CPU on the database and application servers, making the site unresponsive. The search feature is enabled by default. Discourse is affected from 2026.7.0-latest before 2026.7.5, from 2026.9.0-latest before 2026.9.2, and from 2026.10.0-latest before 2026.10.1.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact A denial-of-service vulnerability existed in Discourse's full-text search implementation. The search functionality accepted unbounded input terms, which were passed directly to the underlying database's ranking functions. An attacker could craft a search query combined with specific content patterns to cause excessive CPU consumption on the database and application servers, potentially rendering the site unresponsive. This issue affects sites where the search feature is enabled (enabled by default). No authentication is required to trigger the vulnerability, although existing rate limits may mitigate the frequency of such attacks. ### Workarounds No known workarounds for this issue <!-- patch-triage-lifecycle:05f6b8aece9ac562693d76eadad66624f7ec3b0b53e83df608943d18be598428 --> Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-B2HVFQ0W.

Why it matters now

Fix Fixed Discourse: 2026.11.0-latest.1, 2026.10.1, 2026.9.2 +1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.11.0-latest.1Patch availableGHSA-5549-q35w-w4m6
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-5549-q35w-w4m6
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-5549-q35w-w4m6
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-5549-q35w-w4m6
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-5549-q35w-w4m6
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-5549-q35w-w4m6
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-5549-q35w-w4m6
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-5549-q35w-w4m6

Remediation

Upgrade Discourse to 2026.7.5, 2026.9.2, 2026.10.1 or 2026.11.0-latest.1, depending on the release line in use.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-5549-q35w-w4m6 Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-5549-q35w-w4m6 Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-5549-q35w-w4m6 Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-5549-q35w-w4m6 Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-5549-q35w-w4m6

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences