LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26077: Discourse doesn't ensure webhooks require a token

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.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-26077 affects Discourse sites using certain email provider webhooks. If authentication tokens were missing, attackers could send fake webhook events that raise users’ bounce scores, potentially disabling legitimate outbound email to those users. This is a business continuity and user communication risk, not a data theft issue based on the advisory.

Executive priority

Treat as a timely medium-priority fix for Discourse environments that rely on email delivery. The main risk is disruption of user communications and account notifications. Upgrade promptly, with higher urgency for public sites and Mailpace integrations.

Technical view

Discourse WebhooksController endpoints for SendGrid, Mailjet, Mandrill, Postmark, and SparkPost accepted unauthenticated requests when no token was configured. Mailpace lacked token validation. Fixed versions reject requests with a 406 response when no authentication token is configured. CVSS is 6.5, CWE-287, network exploitable with no privileges or user interaction.

Likely exposure

Exposed Discourse instances before 2025.12.2, 2026.1.1, or 2026.2.0 are relevant, especially if email provider webhook integrations are enabled and tokens are unset. Mailpace users need the fixed version because the advisory says no pre-fix workaround exists for Mailpace.

Exploitation context

The source bundle does not state active exploitation, and this CVE is not marked KEV. Exploitation would target webhook endpoints to forge email bounce-related payloads, causing integrity and availability impact to user email delivery rather than direct system compromise.

Researcher notes

Evidence is limited to the CVE record and GitHub advisory. The advisory names affected endpoints, fixed versions, workaround token settings, and Mailpace exception. No exploit availability or observed exploitation is stated in the provided sources.

Mitigation direction

  • Upgrade Discourse to 2025.12.2, 2026.1.1, 2026.2.0, or later applicable fixed release.
  • Configure authentication tokens for all supported email provider webhook integrations in site settings.
  • Prioritize upgrading Mailpace integrations; the advisory states no pre-fix workaround exists.
  • Review the GitHub advisory for any updated vendor guidance.

Validation and detection

  • Identify all internet-facing Discourse instances and their deployed versions.
  • Check whether SendGrid, Mailjet, Mandrill, Postmark, SparkPost, or Mailpace webhooks are enabled.
  • Verify relevant webhook authentication token settings are configured where supported.
  • After upgrade, confirm missing-token webhook requests are rejected as expected.
  • Review recent bounce-score changes and unexpected email-disable events for anomalies.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-287: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26077 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-26077Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
discoursediscourse< 2025.12.2, >= 2026.1.0-latest, < 2026.1.1, >= 2026.2.0-latest, < 2026.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-287 · source CWE mapping

Improper Authentication

Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.