Read the docs

Privilege escalation in Discourse via scoped API keys

Priority MEDIUM 48Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · GHSA-44qp-4v5j-2rv8. Fix status from GitHub.

Summary

Discourse accepts external_ids when updating a user, so a granular API key limited to users:update can change that user's external login association. An attacker who controls the replacement identity can sign in as the user, and rebinding an administrator account gives full administrator access. Exploitation needs a valid scoped key and an applicable external login provider. Discourse releases from 2026.7.0-latest, 2026.9.0-latest and 2026.10.0-latest onward are affected.

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

Description from the GitHub advisory

### Impact A granular API key authenticated as an administrator and granted users:update could submit external_ids when updating a user. Although the key was limited to user-update operations, the endpoint could use that parameter to change the user’s DiscourseConnect or managed authentication association. If an attacker controlled the replacement external identity, they could subsequently authenticate as the affected user. Rebinding an administrator account could give the attacker full administrator access. Exploitation requires a valid scoped key that can update the target user and an applicable external login provider. The users:create endpoint also accepted external_ids and could reassign an existing managed-provider association; its impact should be described separately. ### Workarounds Until patched, revoke or rotate granular API keys with users:update or users:create access that are held by untrusted integrations. Review restrictions on the users those keys can affect, and inspect external login associations for unexpected changes. If an integration requires these scopes, avoid giving it access to administrator accounts where possible. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-DPIDQ0FE.

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-44qp-4v5j-2rv8
—Discourse>= 2026.10.0-latest2026.10.1Patch availableGHSA-44qp-4v5j-2rv8
—Discourse>= 2026.9.0-latest2026.9.2Patch availableGHSA-44qp-4v5j-2rv8
—Discourse>= 2026.7.0-latest2026.7.5Patch availableGHSA-44qp-4v5j-2rv8
  • Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-44qp-4v5j-2rv8
  • Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-44qp-4v5j-2rv8
  • Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-44qp-4v5j-2rv8
  • Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-44qp-4v5j-2rv8

Remediation

Update Discourse to one of the fixed versions 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5. Until patched, revoke or rotate granular API keys with users:update or users:create access that are held by untrusted integrations.

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

  • Fix · GHSA-44qp-4v5j-2rv8 Discourse Fixed in 2026.11.0-latest.1 Advisory →
  • Fix · GHSA-44qp-4v5j-2rv8 Discourse Fixed in 2026.10.1 Advisory →
  • Fix · GHSA-44qp-4v5j-2rv8 Discourse Fixed in 2026.9.2 Advisory →
  • Fix · GHSA-44qp-4v5j-2rv8 Discourse Fixed in 2026.7.5 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-44qp-4v5j-2rv8

References

Sources

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