Live › vulnerability › CVE-2026-105454
RT (Request Tracker) does not HTML-escape URLs it turns into links in HTML ticket content. A crafted URL can break out of the link and add a script that runs in the browser of anyone who views the ticket history, acting with that user's RT authority.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 16:31 UTC. All times on this page are UTC.
Teams running Request Tracker that accept ticket content, especially HTML email, from people who are not logged in, such as a public-facing queue where CreateTicket or ReplyToTicket is granted to Everyone. Staff who view those tickets in their browser are the ones at risk. Installations that only accept mail from authenticated users or that do not grant those rights to Everyone are less exposed.
No product ranges from the sources yet.
rt --version or the RT package on the host; unknown otherwise.CreateTicket or ReplyToTicket to Everyone, since that lets unauthenticated senders add ticket content.5.0.116.0.4Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
RT's automatic link creation for URLs in HTML ticket content does not HTML-escape the URL it places in the link. A URL crafted to break out of the link's address can add a script that runs when the ticket history is displayed, with no further action by the viewer. Anyone who can add HTML content to a ticket can plant it. That includes an unauthenticated sender of HTML email to any queue that grants CreateTicket or ReplyToTicket to Everyone, which is routine for a queue that accepts mail from the public. The script runs in the session of any user who views the ticket, and can act in RT with that user's authority.
This issue was fixed in version 5.0.11 and 6.0.4
This page as .md · .json · in your agent: get_signal("CVE-2026-105454")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.