Skip to main content
Mallory
MediumVulnerability

CVE-2026-105454: Stored XSS in Request Tracker HTML ticket URL linking

Published Oct 30, 2026 · Updated 18 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days5 mentions · peak 4 in a dayToday
CVSS5.3Medium · v4
EPSS0.44%38th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Best Practical Solutions
IdentifiersCVE-2026-105454CWE-79 · Improper Neutralization of Input…

CVE-2026-105454 is a stored cross-site scripting vulnerability in Request Tracker's automatic URL linking for HTML ticket content. The link-generation logic fails to HTML-escape URLs inserted into generated link addresses. A crafted URL can break out of the address attribute and inject a script that executes when a user views the ticket history, without further interaction. Anyone able to add HTML content to a ticket can store a payload, including unauthenticated email senders where queue permissions permit public ticket creation or replies. The script executes in the viewer's authenticated RT session.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Successful exploitation allows attacker-controlled JavaScript to execute with the viewing user's RT authority. An attacker can perform actions and access or modify information available to that user, with the scope determined by the viewer's permissions. Users viewing attacker-controlled ticket history are exposed without needing to click a malicious link.

Mitigation

If you can’t patch tonight, do this now.

No vendor-specified workaround is identified. Temporarily restrict who can submit HTML ticket content and, where operationally feasible, remove CreateTicket and ReplyToTicket permissions granted to Everyone on publicly accessible queues. These measures reduce unauthenticated delivery opportunities but do not neutralize malicious content already stored in tickets or prevent submissions by other authorized users.

Remediation

Patch, then assume compromise.

Upgrade Request Tracker to the applicable fixed release, RT 5.0.11 or 6.0.4, or a later release containing the fix. The vulnerability description explicitly identifies these releases as fixed, although the advisory's affected-version tables inconsistently include them. Debian request-tracker5 package reporting separately indicates that a distribution-supplied patch is unavailable; verify the distribution package's fix status rather than assuming upstream remediation has been incorporated.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

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.

VendorProductType
Best Practical SolutionsRequest Trackerapplication
FAQ

Frequently asked questions

Is CVE-2026-105454 exploited in the wild?
As of Oct 31, 2026, Mallory has no reports of CVE-2026-105454 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-105454?
As of Oct 31, 2026, Mallory has found no public exploit for CVE-2026-105454.
Is there a patch for CVE-2026-105454?
Upgrade Request Tracker to the applicable fixed release, RT 5.0.11 or 6.0.4, or a later release containing the fix. The vulnerability description explicitly identifies these releases as fixed, although the advisory's affected-version tables inconsistently include them.
What products are affected by CVE-2026-105454?
Best Practical Solutions Request Tracker.
How severe is CVE-2026-105454?
CVE-2026-105454 has a CVSS v4 score of 5.3 (Medium) and an EPSS score of 0.44% (38th percentile) as of Oct 31, 2026.
Activity feed

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
ghsa syntheticNews · Oct 30, 2026GHSA-356j-wm99-9qqcA stored cross-site scripting vulnerability in RT's automatic URL linking allows attackers who can add HTML ticket content to inject scripts that execute when another user views the ticket history, without further interaction. Scripts run with the viewing user's RT authority. Unauthenticated attackers can deliver payloads through HTML email when a queue grants CreateTicket or ReplyToTicket permissions to Everyone.Read more ↗malware newsNews · Oct 30, 2026Vulnerabilities in Request Tracker and RT for Incident Response software - Malware News - Malware Analysis, News and IndicatorsA cross-site scripting vulnerability discovered by CERT Polska, reported among three flaws affecting Request Tracker and RT for Incident Response. The content does not specify which product or versions this individual CVE affects, its exploitation prerequisites, or its impact.Read more ↗cert polskaNews · Oct 30, 2026Vulnerabilities in Request Tracker and RT for Incident Response software | CERT PolskaStored cross-site scripting in Best Practical Solutions Request Tracker's automatic link generation. An attacker able to add HTML ticket content can inject a script that executes when someone views the ticket history, allowing actions with the viewer's RT authority. Unauthenticated exploitation is possible through HTML email where a queue grants CreateTicket or ReplyToTicket to Everyone. The description identifies versions 5.0.11 and 6.0.4 as fixes, although the summary's vulnerable-version ranges inconsistently include those versions.Read more ↗tenable nessus pluginsNews · Oct 30, 2026Linux Distros Unpatched Vulnerability : CVE-2026-105454 | Tenable®A critical vulnerability affecting Debian's request-tracker5 package, with a CVSS v3 base score of 9.8. The vendor indicates it will not be patched, and the advisory states there is no known solution. No technical description of the underlying flaw is provided. Nessus detects exposure based on reported package presence rather than exploitation testing.Read more ↗
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.