Quick answers
- Is CVE-2026-72728 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72728 being exploited in the wild.
- How severe is CVE-2026-72728?
- Medium severity, with a CVSS score of 6.3, published 10 August 2026.
- Which products and versions are affected?
- Discourse < 2026.1.7, >= 2026.6.0 and < 2026.6.2, >= 2026.7.0 and < 2026.7.1.
- Is there a fix for CVE-2026-72728?
- A patch was published on 2026-07-31: Fix committed on 2026-07-31 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72728 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72728?
- 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
The vulnerability exists in Discourse's Onebox feature, which embeds previews of linked content. The allowlist validation for iframe origins used an overly permissive regular expression pattern that failed to properly enforce URL authority boundaries. An authenticated attacker could submit specially-formed URLs that matched the allowlist regex but contained malicious subdomains or path components, bypassing the security controls intended to prevent embedding of arbitrary third-party content. The fix changes the wildcard matching pattern from `\S*` (any non-whitespace) to `[^/?#]*` (characters excluding path/query/fragment delimiters), properly enforcing origin boundary validation. Patches are available in versions 2026.1.7, 2026.6.2, 2026.7.1, and 2026.8.0-latest.1.
Affected products
- Discourse Discourse < 2026.1.7, >= 2026.6.0 and < 2026.6.2, >= 2026.7.0 and < 2026.7.1
Timeline
- 2026-07-31: disclosed
- 2026-07-31: patched: Fix committed on 2026-07-31
- 2026-08-10: advisory: CVE-2026-72728 published