UBUNTU-CVE-2026-105454: Medium severity ubuntu/request-tracker5 vulnerability

Published Nov 3, 2026
·
Updated

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

Affected Software

4 affected components
ubuntu/request-tracker5*
ubuntu/request-tracker5*
ubuntu/request-tracker5*
ubuntu/request-tracker5*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade RT to a version that resolves this vulnerability.

    Fixed in 5.0.11
  2. Upgrade

    Upgrade RT to a version that resolves this vulnerability.

    Fixed in 6.0.4

Event History

Nov 3, 2026
CVE Published
via OSV·12:00 AM
Data Sourced
via OSV·12:00 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

Which deployments are most exposed to unauthenticated exploitation?

Queues that accept email from the public and grant CreateTicket or ReplyToTicket to Everyone are exposed to an unauthenticated sender planting malicious HTML in a ticket. This configuration is described as routine for public-facing mail queues.

2

What must an attacker do to trigger the script after planting it?

The attacker only needs to add crafted HTML content containing a URL designed to break out of the generated link address. The script executes when a user displays the ticket history; the viewer does not need to take further action.

3

What is the impact when a ticket viewer is affected?

The script runs in the session of the user viewing the ticket and can act in RT with that user's authority. Confidentiality and integrity are affected, including across the subsequent system scope indicated by the vector.

4

Which fixed versions are identified?

The issue was fixed in RT version 5.0.11 and 6.0.4.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203