Summary
CVE-2026-55103 is a high-severity (CVSS 8.6) authentication and authorization flaw in the Discourse ActivityPub plugin (discourse-activity-pub). The plugin does not adequately verify the actor on inbound federated requests. As a result, attackers can edit, delete, or reply to federated posts without the required permissions.
Technical details
- Root cause: missing identity and ownership checks when validating the actor of inbound ActivityPub requests (CWE-345 Insufficient Verification of Data Authenticity, CWE-863 Incorrect Authorization).
- Trigger conditions: the Discourse instance runs the discourse-activity-pub plugin and receives inbound federated requests. No privileges or user interaction are required.
- Attack vector: network, unauthenticated, low complexity.
- Impact: an attacker can edit, delete, or reply to federated posts without permission. The CVSS vector scores a changed scope and high confidentiality impact.
- The vendor fix also adds outbound-request SSRF hardening to the plugin.
Affected software
- discourse-activity-pub plugin versions prior to the fix commit
1c8518b0f2abdf31cbea3e0b242f74d8994a9ba5(per the CVE record). The GitHub advisory describes the affected range in terms of commits up to3d5d6e7. - Discourse core is not itself listed as affected. Only instances that have the ActivityPub plugin installed and enabled are relevant.
Severity
- CVSS v3.1 base score: 8.6 (High)
- Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate: update the discourse-activity-pub plugin to the latest version, which includes the fix commit
1c8518b0f2abdf31cbea3e0b242f74d8994a9ba5. This is normally done by updating Discourse and its plugins. - Workarounds: none are documented by the vendor. If you cannot patch immediately, consider disabling the ActivityPub plugin until you can update. This is a general precaution, not a vendor-documented workaround.
- Confirm that any hosted Discourse instances using the plugin have been updated.

