CVE-2026-41075 RT: SQL injection via entry_aggregator parameter in JSON search
Authenticated users can exploit SQL injection in RT to read or modify database data, requiring an upgrade to patched versions.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41075?
CVE-2026-41075 is a high-severity SQL injection vulnerability in bestpractical rt, published on 22 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 through 5.0.9 and 6.0.0 through 6.0.2 contain an SQL injection vulnerability. An authenticated user can craft input that is incorporated into database queries without proper validation, potentially allowing them to read or modify data in the RT database. This issue has been fixed in versions 5.0.10 and 6.0.3. If developers are unable to upgrade immediately, they can temporarily work around this issue by restricting RT account access to trusted users.
Weakness: CWE-89
Which versions are affected by CVE-2026-41075?
How do I fix CVE-2026-41075?
Upgrade to a fixed version.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-41075 being exploited?
There is no known exploitation of CVE-2026-41075 in the wild and no public exploit code.
Sources
Also known as DEBIAN-CVE-2026-41075, GHSA-7vf8-xv7w-97c6, UBUNTU-CVE-2026-41075.