CVE-2025-61598 Discourse is missing Cache-Control response header on error responses
Missing Cache-Control headers on error responses allow proxies to cache sensitive data, potentially leading to cache poisoning and information disclosure.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-61598?
CVE-2025-61598 is a medium-severity vulnerability in Discourse Discourse, published on 28 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Discourse is an open source discussion platform. Version before 3.6.2 and 3.6.0.beta2, default Cache-Control response header with value no-store, no-cache was missing from error responses. This may caused unintended caching of those responses by proxies potentially leading to cache poisoning attacks. This vulnerability is fixed in 3.6.2 and 3.6.0.beta2.
Weakness: CWE-524
Which versions are affected by CVE-2025-61598?
1 open source package ship an affected version, including discourse. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
discourse Bitnami | All versions | 3.6.2 |
Products include Discourse Discourse.
How do I fix CVE-2025-61598?
Upgrade discourse to 3.6.2 or later.
Is CVE-2025-61598 being exploited?
There is no known exploitation of CVE-2025-61598 in the wild and no public exploit code.
Other vulnerabilities in Discourse Discourse
- CVE-2021-41163 RCE via malicious SNS subscription payload
- CVE-2022-36066 Discourse vulnerable to RCE via admins uploading maliciously zipped file
- CVE-2022-39356 Discourse user account takeover via email and invite link
- CVE-2023-22468 Discourse vulnerable to Cross-site Scripting in local oneboxes
- CVE-2026-27934 Discourse leaks private topic title and post excerpt via user action API endpoint
Sources
Also known as BIT-discourse-2025-61598, GHSA-jp9x-wwv6-cv3j.