CVE-2026-26078: Discourse has authentication bypass vulnerability in the Patreon plugin webhook endpoint
Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, when the patreonwebhooksecret site setting is blank, an attacker can forge valid webhook signatures by computing an HMAC-MD5 with an empty string as the key. Since the request body is known to the sender, the attacker can produce a matching signature and send arbitrary webhook payloads. This allows unauthorized creation, modification, or deletion of Patreon pledge data and triggering patron-to-group synchronization. This vulnerability is patched in versions 2025.12.2, 2026.1.1, and 2026.2.0. The fix rejects webhook requests when the webhook secret is not configured, preventing signature forgery with an empty key. As a workaround, configure the patreonwebhooksecret site setting with a strong, non-empty secret value. When the secret is non-empty, an attacker cannot forge valid signatures without knowing the secret.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-26078?
CVE-2026-26078 is considered a medium severity vulnerability due to the potential for attackers to forge valid webhook signatures.
How do I fix CVE-2026-26078?
To fix CVE-2026-26078, update Discourse to version 2025.12.2, 2026.1.1, or 2026.2.0 or later.
What is the impact of CVE-2026-26078 on my Discourse installation?
The impact of CVE-2026-26078 allows an attacker to forge webhook signatures, which can compromise data integrity.
In which versions is CVE-2026-26078 present?
CVE-2026-26078 is present in Discourse versions prior to 2025.12.2, 2026.1.1, and 2026.2.0.
What should I do if I cannot update Discourse to fix CVE-2026-26078?
If you cannot update, ensure the `patreon_webhook_secret` setting is not left blank and consider additional security measures to mitigate the risk.