CVE-2026-44231: Credential Disclosure and Privilege Escalation in Request Tracker REST 2.0
- Vendor
- Best Practical Solutions
An incorrect authorization vulnerability in the Request Tracker (RT) REST 2.0 user collection endpoint allows an authenticated, privileged non-administrative user to obtain authentication credentials belonging to other users, including administrators. The disclosed credentials allow access to data through RT RSS and iCal feed endpoints with the affected users' read permissions. The request that exposes the credentials also rotates them, invalidating previously distributed feed URLs across the instance. Affected versions include RT releases before 5.0.10 and releases from 6.0.0 up to, but excluding, 6.0.3.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Exploitation compromises the confidentiality of user authentication credentials and data accessible through RT feed endpoints, including information available to administrators but not to the attacker’s own account. Credential rotation also invalidates existing feed URLs throughout the instance, disrupting consumers of those feeds. The demonstrated privilege escalation concerns feed-based read access; unrestricted administrative actions or code execution are not established.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, restrict access to the REST 2.0 API user collection endpoint to only fully trusted administrators, minimize the number of non-administrative privileged accounts, and limit exposure of feed functionality to only users and integrations that require it. Monitor for unexpected feed credential rotation or unexplained invalidation of feed URLs, and review access patterns involving REST 2.0 user enumeration and feed access. These measures reduce exposure but do not fully remediate the vulnerability.
Remediation
Patch, then assume compromise.
Upgrade RT to version 5.0.10 or later in the 5.x branch, or 6.0.3 or later in the 6.x branch. Distribution-maintained installations can apply the corresponding security updates: Fedora 43, 44, and 45 provide rt-5.0.10-1.fc43, rt-5.0.10-1.fc44, and rt-5.0.10-1.fc45, respectively. Debian fixes are request-tracker4 4.4.6+dfsg-1.1+deb12u4 for bookworm, request-tracker5 5.0.3+dfsg-3~deb12u6 for bookworm, and request-tracker5 5.0.7+dfsg-4+deb13u3 for trixie. Fedora updates were pending testing at the time of their notices; confirm repository availability.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-44231 exploited in the wild?
- As of Nov 1, 2026, Mallory has no reports of CVE-2026-44231 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-44231?
- As of Nov 1, 2026, Mallory has found no public exploit for CVE-2026-44231.
- Is there a patch for CVE-2026-44231?
- Upgrade RT to version 5.0.10 or later in the 5.x branch, or 6.0.3 or later in the 6.x branch. Distribution-maintained installations can apply the corresponding security updates: Fedora 43, 44, and 45 provide rt-5.0.10-1.fc43, rt-5.0.10-1.fc44, and rt-5.0.10-1.fc45, respectively.
- What products are affected by CVE-2026-44231?
- Best Practical Solutions Request Tracker.
- How severe is CVE-2026-44231?
- CVE-2026-44231 has a CVSS v3.1 score of 9.1 (Critical) and an EPSS score of 0.25% (16th percentile) as of Nov 1, 2026.
Recent activity
13 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.