# CVE-2026-44231: RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint

> Privileged users can steal other users' credentials via the REST API to read data and escalate privileges in RT.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-44231, GHSA-7rx2-x357-wv74, UBUNTU-CVE-2026-44231

## What is CVE-2026-44231?

CVE-2026-44231 is a critical vulnerability in bestpractical rt, published on 20 Jul 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 prior to 5.0.10, 6.0.0 and above, prior to 6.0.3 contain an information disclosure and privilege escalation vulnerability in the REST 2.0 API. A privileged (non-administrative) user can obtain authentication credentials belonging to other users — including users with administrative privileges — and use those credentials to read data as those users via RT's feed endpoints. The same request that exposes the credentials also rotates them, invalidating previously-distributed feed URLs across the instance. This issue has been fixed in versions 5.0.10 and 6.0.3.

Weakness: CWE-863 (Incorrect Authorization), CWE-269 (Improper Privilege Management), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-44231?

It affects 1 product.


Products: Bestpractical Request Tracker.

## How do I fix CVE-2026-44231?

Upgrade to a fixed version.

## Is CVE-2026-44231 being exploited?

There is no known exploitation of CVE-2026-44231 in the wild and no public exploit code.

## Other vulnerabilities in bestpractical rt

- [CVE-2017-5943](https://insights.sbomify.com/CVE-2017-5943/): Information disclosure in n/a (high 8.8)
- [CVE-2017-5944](https://insights.sbomify.com/CVE-2017-5944/): Code injection in n/a (high 8.8)
- [CVE-2023-41259](https://insights.sbomify.com/CVE-2023-41259/): Information disclosure in n/a (high 7.5)
- [CVE-2023-41260](https://insights.sbomify.com/CVE-2023-41260/): Information disclosure in n/a (high 7.5)
- [CVE-2023-45024](https://insights.sbomify.com/CVE-2023-45024/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44231 and fix it if it is affected.

What it is: CVE-2026-44231 is a critical vulnerability in bestpractical rt, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44231 in the wild and no public exploit code.

Affected product: bestpractical rt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44231/ (Markdown: https://insights.sbomify.com/CVE-2026-44231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44231
- OSV: https://osv.dev/vulnerability/CVE-2026-44231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44231/
Summaries are generated and may contain mistakes; the official description above is the record.