Read the docs
TI-2026-21081 Aliases CVE-2026-26077

Discourse doesn't ensure webhooks require a token

Priority LOW 37CWE-287Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-287.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00928 60th percentileScored 2026-11-07
Fix Fixed discourse (discourse): 2025.12.2, 2026.1.1, 2026.2.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
discoursediscoursebefore 2025.12.2; 2026.1.0-latest to before 2026.1.1; 2026.2.0-latest to before 2026.2.02025.12.2, 2026.1.1, 2026.2.0Patch availableCNA
  • discourse Vendordiscourse Affected before 2025.12.2; 2026.1.0-latest to before 2026.1.1; 2026.2.0-latest to before 2026.2.0 Fixed in 2025.12.2, 2026.1.1, 2026.2.0 Patch available CNA

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:discourse:discourse:*:*:*:*:*:*:*:*before 2025.12.0; 2026.1.0 to before 2026.1.1Vulnerablediscourse
cpe:2.3:a:discourse:discourse:2026.2.0:*:*:*:latest:*:*:*2026.2.0Vulnerablediscourse
  • cpe:2.3:a:discourse:discourse:*:*:*:*:*:*:*:* Versions before 2025.12.0; 2026.1.0 to before 2026.1.1 Vulnerable ·discourse
  • cpe:2.3:a:discourse:discourse:2026.2.0:*:*:*:latest:*:*:* Versions 2026.2.0 Vulnerable ·discourse

Remediation

  • Fix · CNA discourse (discourse) Fixed in 2025.12.2, 2026.1.1, 2026.2.0

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-26077
  2. 2026-10-13 EPSS moved to the 50th–90th percentile

References

Advisory 1

  • TI-2021-19656 Denial of Service in discourse CVSS 3.1MEDIUM 6.8
  • TI-2024-36150 Potential Backup file leaked via Nginx in Discourse CVSS 3.1HIGH 7.5
  • TI-2021-18002 RCE via malicious SNS subscription payload CVSS 3.1CRITICAL 10.0
  • TI-2026-24651 Discourse: Open redirect via `sso_destination_url` cookie in `enter` CVSS 4.0MEDIUM 5.1
  • TI-2026-22278 Discourse leaks private topic title and post excerpt via user action API endpoint CVSS 4.0HIGH 8.7
  • TI-2023-24152 Unauthenticated access to new private chat messages in Discourse CVSS 3.1HIGH 7.5
See all 262 →

Sources

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