Admin takeover via user API keys in Discourse
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-6xwm-rw64-6mhg. Fix status from GitHub.
Summary
Discourse contains a parameter handling flaw in the User API Key device authorization flow. An authenticated user who may create user API keys, which by default includes Trust Level 0 users on sites with open registration, can authorize a device key for a different user account. The resulting key carries the victim's access and privileges, which can expose data and allow unauthorized actions.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact A vulnerability exists in the User API Key device authorization flow in Discourse. An authenticated user with permission to create user API keys (by default, this includes Trust Level 0 users on sites with open registration) could exploit a parameter handling flaw to authorize a device key for a different user account. The resulting key grants the attacker the same access and privileges as the victim, leading to potential data exposure and unauthorized actions within the application. ### Workarounds No known workarounds for this issue Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-2RCWW0D2.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | Discourse | — | 2026.11.0-latest.1 | Patch available | GHSA-6xwm-rw64-6mhg |
| — | Discourse | >= 2026.10.0-latest | 2026.10.1 | Patch available | GHSA-6xwm-rw64-6mhg |
| — | Discourse | >= 2026.9.0-latest | 2026.9.2 | Patch available | GHSA-6xwm-rw64-6mhg |
| — | Discourse | >= 2026.7.0-latest | 2026.7.5 | Patch available | GHSA-6xwm-rw64-6mhg |
- Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-6xwm-rw64-6mhg
- Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-6xwm-rw64-6mhg
- Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-6xwm-rw64-6mhg
- Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-6xwm-rw64-6mhg
Remediation
Upgrade Discourse to 2026.11.0-latest.1, 2026.10.1, 2026.9.2 or 2026.7.5, depending on the release line in use. The sources list no workaround for this issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-6xwm-rw64-6mhg Discourse Fixed in 2026.11.0-latest.1 Advisory →
- Fix · GHSA-6xwm-rw64-6mhg Discourse Fixed in 2026.10.1 Advisory →
- Fix · GHSA-6xwm-rw64-6mhg Discourse Fixed in 2026.9.2 Advisory →
- Fix · GHSA-6xwm-rw64-6mhg Discourse Fixed in 2026.7.5 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-6xwm-rw64-6mhg
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences