CVE-2026-26077 PUBLISHED

Discourse doesn't ensure webhooks require a token

Assigner: GitHub_M
Reserved: 10.02.2026 Published: 26.02.2026 Updated: 26.02.2026

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, several webhook endpoints (SendGrid, Mailjet, Mandrill, Postmark, SparkPost) in the WebhooksController accepted requests without a valid authentication token when no token was configured. This allowed unauthenticated attackers to forge webhook payloads and artificially inflate user bounce scores, potentially causing legitimate user emails to be disabled. The Mailpace endpoint had no token validation at all. Starting in versions 2025.12.2, 2026.1.1, and 2026.2.0, all webhook endpoints reject requests with a 406 response when no authentication token is configured. As a workaround, ensure that webhook authentication tokens are configured for all email provider integrations in site settings (e.g., sendgrid_verification_key, mailjet_webhook_token, postmark_webhook_token, sparkpost_webhook_token). There's no current workaround for mailpace before getting this fix.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CVSS Score: 6.5

Product Status

Vendor discourse
Product discourse
Versions
  • Version < 2025.12.2 is affected
  • Version >= 2026.1.0-latest, < 2026.1.1 is affected
  • Version >= 2026.2.0-latest, < 2026.2.0 is affected

References

Problem Types

  • CWE-287: Improper Authentication CWE