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

request-tracker4 Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-44231: ... 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Request Tracker (RT) is a widely used open-source ticketing system that helps organizations manage tasks and issues efficiently. It provides features such as ticket creation, tracking, and reporting, making it essential for IT service management and customer support. The vulnerability identified as CVE-2026-44231 affects multiple versions of Request Tracker, specifically request-tracker4 and request-tracker5 across various Debian distributions, potentially compromising the integrity and security of systems utilizing these packages.

Vulnerability Detail

CVE-2026-44231 is a security vulnerability that arises from inadequate input validation in the Request Tracker software. This flaw can be exploited by attackers to execute arbitrary code or perform unauthorized actions within the system. The vulnerability is present in both request-tracker4 and request-tracker5 packages across Debian distributions, including Bullseye, Bookworm, Trixie, and Forky. If left unaddressed, this vulnerability could lead to severe data breaches, unauthorized access, and significant operational disruptions.

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

If immediate patching is not feasible, consider disabling the affected services temporarily or restricting access to the Request Tracker application until a fix can be applied. Additionally, review user permissions and limit access to trusted users only.

Conclusion

CVE-2026-44231 poses a significant risk to systems using Request Tracker packages. It is essential to update to the latest patched versions to safeguard against potential exploits. Regular monitoring and prompt action can help mitigate the risks associated with this vulnerability.

See every vulnerability recorded for request-tracker4 →

Share this vulnerability

FAQ

CVE-2026-44231 is a security vulnerability affecting Request Tracker packages that can allow unauthorized actions or code execution.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

If exploited, this vulnerability could lead to data breaches, unauthorized access, and operational disruptions within your organization.

Yes, patches are available for the affected packages. Ensure to update to the latest versions of request-tracker4 or request-tracker5.

Consider disabling the affected services temporarily or restricting access to the application until the patch can be applied.

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