Quick answers
- Is CVE-2026-91133 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91133 being exploited in the wild.
- How severe is CVE-2026-91133?
- Medium severity, with a CVSS score of 6.5, published 24 September 2026.
- Which products and versions are affected?
- Discourse before 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0.
- Is there a fix for CVE-2026-91133?
- A patch was published on 2026-08-25: Security fixes committed Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-91133 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-91133?
- Check whether you run Discourse at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authenticated user could supply unescaped SQL LIKE metacharacters to upload-resolution patterns, causing wildcard matching to select unrelated uploads. The vulnerability affects URL-lookup, upload metadata resolution, and cooked-video-placeholder paths, all using unsanitized string interpolation in LIKE queries. The fix escapes LIKE metacharacters via sanitize_sql_like() before query execution.
Affected products
- Discourse Discourse before 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0
Timeline
- 2026-09-24: disclosed
- 2026-08-25: patched: Security fixes committed