Read the docs

Denial of service in Discourse through RSA key generation

Priority LOW 38Published · Updated

Key facts

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

No CVSS vector from any source. Fix status from GitHub.

Summary

Discourse releases from 2026.7.0-latest onward are affected. Several endpoints pass the unvalidated public_key request parameter to OpenSSL::PKey::RSA.new, which generates a new RSA keypair when given an integer. An unauthenticated remote attacker can send a large integer to force seconds of key generation per request, tying up Puma workers and degrading or denying service.

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

Description from the GitHub advisory

Passing an integer to `OpenSSL::PKey::RSA.new` generates a new RSA keypair of that bit length rather than parsing an existing key. Several endpoints fed the unvalidated `public_key` request param straight into this call, so an unauthenticated attacker could send a large integer (e.g. a multi-kilobit "key") and force the server to spend seconds generating a keypair per request, tying up Puma workers and degrading or denying service. The most severe path was `ApplicationController#redirect_to_login_if_required`, which handled `user_api_public_key` on anonymous requests with no rate limiting. The user API key client creation endpoint and the device auth flow had the same pattern. ### Workarounds None. Sites can mitigate by rate-limiting unauthenticated requests at the proxy, but the vulnerable paths ran before rate limiting on the worst endpoint. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-DJF9HY4Q.

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-fx7j-6fh9-xwvm
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-fx7j-6fh9-xwvm
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-fx7j-6fh9-xwvm
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-fx7j-6fh9-xwvm
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-fx7j-6fh9-xwvm
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-fx7j-6fh9-xwvm
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-fx7j-6fh9-xwvm
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-fx7j-6fh9-xwvm

Remediation

Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, matching the release line in use. Sites that cannot upgrade can rate-limit unauthenticated requests at the proxy.

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

  • Fix · GHSA-fx7j-6fh9-xwvm Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-fx7j-6fh9-xwvm Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-fx7j-6fh9-xwvm Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-fx7j-6fh9-xwvm Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-fx7j-6fh9-xwvm

References

Sources

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