Read the docs

Crafted regular expressions corrupt memory in Discourse server

Priority MEDIUM 46Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · GHSA-jf8q-52mm-v752. Fix status from GitHub.

Summary

Discourse versions from 2026.7.0-latest onward are affected. Specially crafted regular expressions cause memory corruption in the server, which can lead to denial of service and possibly remote code execution. Only admin and moderator users can trigger it, so the risk is mainly for shared-hosting environments where admins may not be trusted.

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

Description from the GitHub advisory

Specially crafted regular expressions could lead to memory corruption in the server. This could lead to Denial of Service, and could potentially be escalated to RCE. For more information, see https://www.ruby-lang.org/en/news/2026/10/23/regexp-fixes-for-gitlab-cves/ In Discourse, this is exploitable only by admin/moderator users. Therefore, this security advisory is primarily a concern for shared-hosting environments where admins may not be trusted. This is resolved by a Ruby patch, which is available in `discourse/base:2.0.20261022-1808` and later. On a standard install, run `./launcher rebuild app` to get the latest version. Web-based updates will be unavailable until this rebuild has been completed.

Why it matters now

Fix Fixed Discourse: 2026.10.0-latest.1, 2026.9.1, 2026.8.2 +1

SSVC decision points

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

Affected products

VendorProductAffected versionsFixed inStatusSource
—Discourse—2026.10.0-latest.1Patch availableGHSA-jf8q-52mm-v752
—Discourse>= 2026.9.0-latest2026.9.1Patch availableGHSA-jf8q-52mm-v752
—Discourse>= 2026.8.0-latest2026.8.2Patch availableGHSA-jf8q-52mm-v752
—Discourse>= 2026.7.0-latest2026.7.4Patch availableGHSA-jf8q-52mm-v752
  • Discourse Vendor— Affected — Fixed in 2026.10.0-latest.1 Patch available GHSA-jf8q-52mm-v752
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.1 Patch available GHSA-jf8q-52mm-v752
  • Discourse Vendor— Affected >= 2026.8.0-latest Fixed in 2026.8.2 Patch available GHSA-jf8q-52mm-v752
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.4 Patch available GHSA-jf8q-52mm-v752

Remediation

Install the fixed release for your line: 2026.10.0-latest.1, 2026.9.1, 2026.8.2 or 2026.7.4. The fix is a Ruby patch included in discourse/base:2.0.20261022-1808 and later, so on a standard install run ./launcher rebuild app. Web-based updates are unavailable until this rebuild completes.

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

  • Fix · GHSA-jf8q-52mm-v752 Discourse Fixed in 2026.10.0-latest.1 Advisory →
  • Fix · GHSA-jf8q-52mm-v752 Discourse Fixed in 2026.9.1 Advisory →
  • Fix · GHSA-jf8q-52mm-v752 Discourse Fixed in 2026.8.2 Advisory →
  • Fix · GHSA-jf8q-52mm-v752 Discourse Fixed in 2026.7.4 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-jf8q-52mm-v752

References

Sources

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