Callback paths in Discourse oauth2-basic call Ruby methods
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-w69f-7gf7-8xwj. Fix status from GitHub.
Summary
The bundled oauth2-basic plugin in Discourse misuses OAuth2 callback path settings, so the flaw lets a site administrator read server secrets, environment variables and files and invoke Ruby methods with side effects. Discourse versions 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 are affected. Exploitation requires a full administrator account, and hosted or multisite installations where administrators do not control the server are impacted. The plugin is disabled by default.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact A site administrator can misuse OAuth2 callback path settings to read server secrets, environment variables, and files, and invoke Ruby methods with side effects. Hosted and multisite installations are impacted where site administrators do not control the server. Exploitation requires a full administrator account. The bundled plugin is disabled by default. ### Patches The fix limits callback paths to reading token-response data. Users should upgrade to patched versions. ### Workarounds Server operators can apply the patch manually or disable the plugin at the deployment level. Turning it off in site settings is insufficient because an administrator can re-enable it. Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-QLGMPQRV.
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-w69f-7gf7-8xwj |
| — | Discourse | >= 2026.10.0-latest | 2026.10.1 | Patch available | GHSA-w69f-7gf7-8xwj |
| — | Discourse | >= 2026.9.0-latest | 2026.9.2 | Patch available | GHSA-w69f-7gf7-8xwj |
| — | Discourse | >= 2026.7.0-latest | 2026.7.5 | Patch available | GHSA-w69f-7gf7-8xwj |
- Discourse Vendor— Affected — Fixed in 2026.11.0-latest.1 Patch available GHSA-w69f-7gf7-8xwj
- Discourse Vendor— Affected >= 2026.10.0-latest Fixed in 2026.10.1 Patch available GHSA-w69f-7gf7-8xwj
- Discourse Vendor— Affected >= 2026.9.0-latest Fixed in 2026.9.2 Patch available GHSA-w69f-7gf7-8xwj
- Discourse Vendor— Affected >= 2026.7.0-latest Fixed in 2026.7.5 Patch available GHSA-w69f-7gf7-8xwj
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. Server operators can apply the patch manually or disable the plugin at the deployment level, since turning it off in site settings is insufficient because an administrator can re-enable it.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-w69f-7gf7-8xwj Discourse Fixed in 2026.11.0-latest.1 Advisory →
- Fix · GHSA-w69f-7gf7-8xwj Discourse Fixed in 2026.10.1 Advisory →
- Fix · GHSA-w69f-7gf7-8xwj Discourse Fixed in 2026.9.2 Advisory →
- Fix · GHSA-w69f-7gf7-8xwj Discourse Fixed in 2026.7.5 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-w69f-7gf7-8xwj
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences