CVE-2026-41076

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.9 and prior in addition to 6.0.0 through 6.0.2 contain an authentication bypass vulnerability in RT installations that use LDAP/AD for user authentication. Under certain LDAP server configurations, an attacker may be able to authenticate as any LDAP-backed RT user without supplying valid credentials. 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 reviewing their LDAP server's authentication policy to ensure it rejects unauthenticated bind attempts. Upgrading RT remains the recommended fix.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
49%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jun 3, 2026
Patch available. Sources: github_release, github.
github_release Patch Available

rt-6.0.3

Patch available: bestpractical/rt rt-6.0.3

https://github.com/bestpractical/rt/releases/tag/rt-6.0.3
github_release Patch Available

rt-5.0.10

Patch available: bestpractical/rt rt-5.0.10

https://github.com/bestpractical/rt/releases/tag/rt-5.0.10
github Patch Available

LDAP authentication bypass via empty password · Advisory · bestpractical/rt · GitHub

https://github.com/bestpractical/rt/security/advisories/GHSA-3w28-fmcr-mjjx

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturt5-standalone (5.0.5+dfsg-2ubuntu0.1~esm2) @ noble2026-08-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
request-tracker44.4.6+dfsg-1.1, 4.4.6+dfsg-1.1+deb12u1, 4.4.6+dfsg-1.1+deb12u2, 4.4.6+dfsg-1.1+deb12u34.4.6+dfsg-1.1+deb12u4—
request-tracker55.0.3+dfsg-2 ... 5.0.3+dfsg-3~deb12u5 (6 versions)5.0.3+dfsg-3~deb12u6—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
request-tracker44.4.4+dfsg-2 ... 4.4.7+dfsg-4 (16 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
request-tracker55.0.7+dfsg-4, 5.0.7+dfsg-4+deb13u1, 5.0.7+dfsg-4+deb13u25.0.7+dfsg-4+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
request-tracker55.0.7+dfsg-4 ... 5.0.9+dfsg-4 (7 versions)5.0.10+dfsg-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 188 total refreshes for this CVE.

  1. 2026-09-23 17:53 UTCEPSS rescore
  2. 2026-09-20 20:15 UTCEPSS rescore
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-13 16:47 UTCEPSS rescore
  9. 2026-09-12 15:01 UTCEPSS rescore
  10. 2026-09-11 14:53 UTCEPSS rescore
  11. 2026-09-11 09:37 UTCEPSS rescore
  12. 2026-09-11 03:53 UTCOSV refresh
  13. 2026-09-10 09:34 UTCEPSS rescore
  14. 2026-09-08 22:00 UTCEPSS rescore
  15. 2026-09-07 16:01 UTCEPSS rescore
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:12 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-28 21:41 UTCEPSS rescore
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-23 16:40 UTCEG score recompute
  3. 2026-08-23 16:40 UTCVendor advisory
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 21:40 UTCEG score recompute
  7. 2026-08-21 21:40 UTCVendor advisory
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 18:38 UTCEG score recompute
  10. 2026-08-20 18:38 UTCVendor advisory
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 09:43 UTCVendor advisory
  15. 2026-08-16 16:48 UTCEG score recompute
  16. 2026-08-16 16:48 UTCVendor advisory
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 03:19 UTCEG score recompute
  19. 2026-08-16 03:19 UTCVendor advisory
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 03:04 UTCEG score recompute
  22. 2026-08-15 03:04 UTCVendor advisory
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 14:26 UTCVendor advisory
  25. 2026-08-14 01:52 UTCEG score recompute
  26. 2026-08-14 01:52 UTCVendor advisory
  27. 2026-08-13 22:00 UTCEPSS rescore
  28. 2026-08-13 03:29 UTCVendor advisory
  29. 2026-08-12 14:55 UTCEG score recompute
  30. 2026-08-12 14:55 UTCVendor advisory
  31. 2026-08-12 13:51 UTCEPSS rescore
  32. 2026-08-12 02:20 UTCVendor advisory
  33. 2026-08-11 13:46 UTCEG score recompute
  34. 2026-08-11 13:46 UTCVendor advisory
  35. 2026-08-11 13:43 UTCEPSS rescore
  36. 2026-08-11 00:28 UTCEG score recompute
  37. 2026-08-11 00:28 UTCVendor advisory
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 02:28 UTCVendor advisory
  40. 2026-08-09 13:54 UTCEG score recompute
  41. 2026-08-09 13:54 UTCVendor advisory
  42. 2026-08-09 13:46 UTCEPSS rescore
  43. 2026-08-09 01:20 UTCEG score recompute
  44. 2026-08-09 01:20 UTCVendor advisory
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 01:58 UTCEG score recompute
  47. 2026-08-08 01:58 UTCVendor advisory
  48. 2026-08-07 13:23 UTCVendor advisory
  49. 2026-08-07 00:49 UTCEG score recompute
  50. 2026-08-07 00:49 UTCVendor advisory
  51. 2026-08-06 13:46 UTCEPSS rescore
  52. 2026-08-06 09:50 UTCVendor advisory
  53. 2026-08-05 21:10 UTCEG score recompute
  54. 2026-08-05 21:10 UTCVendor advisory
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 10:38 UTCEPSS rescore
  58. 2026-08-04 05:25 UTCVendor advisory
  59. 2026-08-03 16:46 UTCEG score recompute
  60. 2026-08-03 16:46 UTCVendor advisory
  61. 2026-08-03 10:36 UTCEPSS rescore
  62. 2026-08-02 18:19 UTCVendor advisory
  63. 2026-08-02 05:44 UTCEG score recompute
  64. 2026-08-02 05:44 UTCVendor advisory
  65. 2026-08-02 02:27 UTCEPSS rescore
  66. 2026-08-01 17:10 UTCEG score recompute
  67. 2026-08-01 17:10 UTCVendor advisory
  68. 2026-08-01 04:16 UTCEPSS rescore
  69. 2026-07-30 16:28 UTCEPSS rescore
  70. 2026-07-30 01:30 UTCEPSS rescore
  71. 2026-07-29 17:29 UTCEG score recompute
  72. 2026-07-28 15:36 UTCEPSS rescore
  73. 2026-07-27 14:13 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41076?
CVE-2026-41076 is a high vulnerability published on May 22, 2026. RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.9 and prior in addition to 6.0.0 through 6.0.2 contain an authentication bypass vulnerability in RT installations that use LDAP/AD for user authentication. Under certain LDAP server configurations, an attacker may…
When was CVE-2026-41076 disclosed?
CVE-2026-41076 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41076 actively exploited?
CVE-2026-41076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.7% of all scored CVEs.
What is the CVSS score of CVE-2026-41076?
CVE-2026-41076 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-41076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41076, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41076

Explore →

Is Your Infrastructure Affected by CVE-2026-41076?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs