Discourse: Reject literal backslash path separators in iframe src traversal guard
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.
Discourse is an open-source discussion platform. Prior to 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0, the iframe src traversal guard did not treat literal backslashes as path separators after decoded dot segments. A crafted source could therefore pass an allowed_iframes subpath check while browser URL normalization moved the iframe outside the intended allowed path. The resulting iframe could load content from a location that the administrator did not allow. This issue is fixed in versions 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| discourse | <2026.8.0, >=2026.1.0-latest <2026.1.8, >=2026.6.0-latest <2026.6.3, >=2026.7.0-latest <2026.7.2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket