# CVE-2026-44227: RT: Reflected Cross-Site Scripting via URL parameters

> Attackers can execute arbitrary JavaScript in authenticated users' browsers via crafted URLs, potentially leading to session hijacking or account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-7742-fhq7-ggv9, UBUNTU-CVE-2026-44227

## What is CVE-2026-44227?

CVE-2026-44227 is a medium-severity cross-site scripting vulnerability in bestpractical rt, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

RT is an open source, enterprise-grade issue and ticket tracking system. Versions 6.0.0 and above, prior to 6.0.3 contain a reflected Cross-Site Scripting (XSS) vulnerability. An attacker who can induce an authenticated RT user to visit a crafted URL can execute arbitrary JavaScript in that user's browser session. There are no effective workarounds. Avoid following untrusted RT URLs. This issue has been fixed in version 6.0.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Bestpractical Request Tracker.

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

No fix has been published for CVE-2026-44227 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44227 being exploited?

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

## Other vulnerabilities in bestpractical rt

- [CVE-2026-44231](https://insights.sbomify.com/CVE-2026-44231/): RT: Privilege escalation and information disclosure via REST 2.0 user collection endpoint (critical 9.1)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44227 is a medium-severity cross-site scripting vulnerability in bestpractical rt, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-44227 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-44227/ (Markdown: https://insights.sbomify.com/CVE-2026-44227/index.md)
```

## Sources

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

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