dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-41075

HIGH · 8.8 CVSS v3.1 Published 2026-05-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 through 5.0.9 and 6.0.0 through 6.0.2 contain an SQL injection vulnerability. An authenticated user can craft input that is incorporated into database queries without proper validation, potentially allowing them to read or modify data in the RT database. This issue has been fixed in versions 5.0.10 and 6.0.3. If developers are unable to upgrade immediately, they can temporarily work around this issue by restricting RT account access to trusted users.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RT (Request Tracker) versions 5.0.0-5.0.9 and 6.0.0-6.0.2 contain an SQL injection vulnerability where authenticated users can craft malicious input that gets incorporated into database queries without proper validation, potentially allowing unauthorized data read or modification in the RT database.

MitigationUpgrade to RT version 5.0.10 or 6.0.3. If immediate upgrade is not feasible, restrict RT account access to trusted users only as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed RT version
    Run 'rt-version' command line tool, or check the version displayed on the RT web interface login page, or inspect the RT.pm file in the lib directory for the $VERSION variable
    Affected if The version is 5.0.0 through 5.0.9, or 6.0.0 through 6.0.2
  2. Confirm RT web interface is accessible
    Attempt to reach the RT server URL (typically /rt/) in a web browser or via curl; verify the login page loads
    Affected if The RT web interface is exposed and accepts authentication requests
  3. Verify user authentication is enabled
    Check RT_SiteConfig.pm for $WebRemoteUserAuth or $RT::WebRemoteUserAuth settings; confirm normal username/password login is not disabled
    Affected if Users can authenticate to RT (whether via local accounts, LDAP, or other methods)
  4. Review RT database user privileges
    Check the database connection credentials used by RT in RT_SiteConfig.pm ($DatabaseUser) and verify what tables that database user has access to
    Affected if The RT database user has broad privileges beyond read-only access (since SQL injection could modify or exfiltrate data)

You are affected if your RT installation runs version 5.0.0-5.0.9 or 6.0.0-6.0.2 and allows authenticated user access to the web interface.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to RT version 5.0.10 or 6.0.3. If immediate upgrade is not feasible, restrict RT account access to trusted users only as a temporary workaround.

Recommended fix High confidence

Upgrade to RT 5.0.10 (if on 5.x) or RT 6.0.3 (if on 6.x)

  1. 1. Identify current RT version by checking the version file or RT admin interface
  2. 2. If running version 5.0.0-5.0.9, plan upgrade to version 5.0.10
  3. 3. If running version 6.0.0-6.0.2, plan upgrade to version 6.0.3
  4. 4. Backup the RT database and configuration files before upgrading
  5. 5. Review RT upgrade documentation for your specific version jump
  6. 6. Download the appropriate fixed release from the official RT repository (best Practical Solutions)
  7. 7. Follow standard RT upgrade procedures to install the new version
  8. 8. Verify the upgrade was successful and RT functions normally
Caveat Patch releases typically contain only bug and security fixes with minimal risk, but review release notes for any configuration changes needed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41075 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data