# CVE-2026-44231: Best Practical RT privilege escalation in REST 2.0 API

Source: https://junglewise.ai/threats/cve-2026-44231-best-practical-rt-privilege-escalation-in-rest-2-0-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-20. Updated: 2026-07-20  
License: CC BY 4.0 with a link back

CVE-2026-44231 · Severity: critical · CVSS 9.1 · Published 2026-07-20

Request Tracker (RT), a widely used enterprise ticket and issue tracking system, contains a security flaw in its programming interface. This vulnerability allows a standard user to steal the login credentials of other users, including system administrators. An attacker could use these stolen credentials to access sensitive internal data and private ticket information, potentially leading to a significant breach of corporate confidentiality.

Technologies: [Best Practical Solutions Request Tracker](https://junglewise.ai/threats/technologies/request-tracker). Vendors: [Best Practical Solutions](https://junglewise.ai/threats/vendors/best-practical-solutions).

## Quick answers

**Is CVE-2026-44231 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44231 being exploited in the wild.

**How severe is CVE-2026-44231?** Critical severity, with a CVSS score of 9.1, published 20 July 2026.

**Which products and versions are affected?** Best Practical Solutions Request Tracker < 5.0.10, >= 6.0.0, < 6.0.3.

**Is there a fix for CVE-2026-44231?** A patch was published on 2026-05-20: Versions 5.0.10 and 6.0.3 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-44231 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-44231?** Check whether you run Best Practical Solutions Request Tracker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

An information disclosure and privilege escalation vulnerability exists in the REST 2.0 user collection endpoint of Best Practical RT. The flaw allows a privileged (but non-administrative) user to retrieve authentication credentials belonging to other users, including administrators, via the REST 2.0 API. These credentials can then be used to access data through RT's RSS and iCal feed endpoints. Exploitation also triggers a rotation of the exposed credentials, which may cause service disruption by invalidating existing legitimate feed URLs. The issue is fixed in versions 5.0.10 and 6.0.3.

## Affected products

- Best Practical RT (Request Tracker) < 5.0.10, >= 6.0.0, < 6.0.3

## Timeline

- 2026-05-20: patched: Versions 5.0.10 and 6.0.3 released
- 2026-05-20: advisory: GitHub Security Advisory published
- 2026-07-20: disclosed: NVD publication date

## References

- [https://github.com/bestpractical/rt/releases/tag/rt-6.0.3](https://github.com/bestpractical/rt/releases/tag/rt-6.0.3)
- [https://github.com/bestpractical/rt/security/advisories/GHSA-7rx2-x357-wv74](https://github.com/bestpractical/rt/security/advisories/GHSA-7rx2-x357-wv74)

## Related threats

- [Request Tracker stored XSS via unescaped URL in automatic links](https://junglewise.ai/threats/cve-2026-105454-rt-s-automatic-link-creation-for-urls-in-html-ticket-content)
- [Best Practical RT stored XSS via inline uploaded content](https://junglewise.ai/threats/cve-2026-44229-best-practical-rt-stored-xss-via-inline-uploaded-content)
- [Best Practical RT SQL injection in JSON search entry_aggregator](https://junglewise.ai/threats/cve-2026-41075-best-practical-rt-sql-injection-in-json-search-entry-aggregator)
- [Best Practical RT Cross-Site Request Forgery](https://junglewise.ai/threats/cve-2026-41074-best-practical-rt-cross-site-request-forgery)
- [Best Practical Request Tracker reflected XSS in Page parameter](https://junglewise.ai/threats/cve-2026-6841-best-practical-request-tracker-reflected-xss-in-page-parameter)