CVE-2026-91133 Discourse: Escape LIKE metacharacters in upload paths to prevent disclosure
Authenticated attackers can inject SQL LIKE wildcards to access unauthorized upload metadata, including filenames and secure paths.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-91133?
CVE-2026-91133 is a medium-severity SQL injection vulnerability in discourse, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Discourse is an open-source discussion platform. Prior to 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0, authenticated users could supply unescaped SQL LIKE metacharacters to upload-resolution patterns, causing wildcard input to select unrelated upload records instead of matching a literal identifier. The affected upload metadata, URL-lookup, and cooked-video-placeholder paths could resolve uploads the user was not authorized to access. This allowed disclosure of restricted metadata, including original filenames and secure-upload paths, without modifying the upload records. This issue is fixed in versions 2026.1.8, 2026.6.3, 2026.7.2, and 2026.8.0.
Weakness: CWE-943
Which versions are affected by CVE-2026-91133?
1 open source package ship an affected version, including discourse.
| Package | Affected | Fixed in |
|---|---|---|
discourse Bitnami | All versions | 2026.8.0 |
How do I fix CVE-2026-91133?
Upgrade discourse to 2026.8.0 or later.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-91133 being exploited?
There is no known exploitation of CVE-2026-91133 in the wild and no public exploit code.
Sources
Also known as BIT-discourse-2026-91133, GHSA-8hxh-573g-52gx.