CVE-2026-32113 discourse CVE debrief

Who should care

Users of the Discourse open-source discussion platform, particularly those who have not updated to the patched versions 2026.1.3, 2026.2.2, or 2026.3.0, should be aware of this vulnerability and take necessary precautions to protect their systems.

Technical summary

The vulnerability exists in the StaticController of the Discourse platform, where the enter action reads the sso_destination_url cookie and redirects to it without proper validation. This allows attackers to set the cookie and redirect users to arbitrary URLs. The issue affects versions from 2026.1.0-latest to before 2026.1.3, 2026.2.0-latest to before 2026.2.2, and 2026.3.0-latest to before 2026.3.0. The patched versions are 2026.1.3, 2026.2.2, and 2026.3.0.

Defensive priority

Medium

Recommended defensive actions

• Update to patched versions 2026.1.3, 2026.2.2, or 2026.3.0
• Verify and restrict access to the sso_destination_url cookie
• Monitor for suspicious redirects and user activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record was published on 2026-03-31T18:16:49.363Z and last modified on 2026-07-24T20:10:00.147Z. The NVD entry is currently Analyzed. The enter action in StaticController reads the sso_destination_url cookie and redirects to it with allow_other_host: true without validating the destination URL, which can be set by attackers. This issue has been patched in versions 2026.1.3, 2026.2.2, and 2026.3.0. Users should verify and restrict access to the sso_destination_url cookie and monitor for suspicious redirects and user activity.

Official resources