Critical Vulnerability in Request Tracker Packages: CVE-2026-41075

request-tracker4 Updated 22 Oct 2026

Summary

20/05/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-41075: ... Affects request-tracker4 versions 4.4.4+dfsg-2 – 4.4.7+dfsg-4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Request Tracker (RT) is a widely used open-source ticketing system that helps organizations manage tasks and requests efficiently. It provides features such as ticket creation, tracking, and reporting, making it a vital tool for IT service management and customer support. However, certain versions of Request Tracker have been identified as vulnerable to CVE-2026-41075, which could potentially compromise the security of systems utilizing these packages.

Vulnerability Detail

CVE-2026-41075 is a security vulnerability affecting multiple versions of the Request Tracker packages (request-tracker4 and request-tracker5) across various Debian distributions. The vulnerability originates from insufficient input validation, which could allow an attacker to execute arbitrary code or perform unauthorized actions within the application. This could lead to data breaches, service disruptions, or unauthorized access to sensitive information. The vulnerability has been classified as critical due to its potential impact on system integrity and confidentiality.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users may restrict access to the affected Request Tracker instances by implementing firewall rules or modifying server configurations to limit exposure to untrusted networks. However, this is not a permanent solution and should only be considered until the packages can be updated.

Conclusion

CVE-2026-41075 poses a significant risk to users of Request Tracker packages across multiple Debian distributions. It is crucial for organizations to update their systems to the patched versions of the affected packages to safeguard against potential exploits. Additionally, utilizing tools like Vulert can help monitor and alert for open-source vulnerabilities in real-time.

See every vulnerability recorded for request-tracker4 →

Share this vulnerability

FAQ

CVE-2026-41075 is a critical vulnerability affecting Request Tracker packages that could allow attackers to execute arbitrary code.

The vulnerability affects request-tracker4 and request-tracker5 across Debian distributions 11, 12, 13, and 14.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If immediate updates are not possible, consider implementing temporary workarounds such as restricting access to the affected instances.

Detailed information about CVE-2026-41075 can be found in the Debian security advisories and the official CVE database.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback