CVE-2026-44231

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

RT is an open source, enterprise-grade issue and ticket tracking system. Versions prior to 5.0.10, 6.0.0 and above, prior to 6.0.3 contain an information disclosure and privilege escalation vulnerability in the REST 2.0 API. A privileged (non-administrative) user can obtain authentication credentials belonging to other users — including users with administrative privileges — and use those credentials to read data as those users via RT's feed endpoints. The same request that exposes the credentials also rotates them, invalidating previously-distributed feed URLs across the instance. This issue has been fixed in versions 5.0.10 and 6.0.3.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 20, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github.
github Patch Available

Privilege escalation and information disclosure via REST 2.0 user collection endpoint · Advisory · bestpractical/rt · GitHub

https://github.com/bestpractical/rt/security/advisories/GHSA-7rx2-x357-wv74
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

Patch Availability(1)

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

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(3)

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 11× in last 7d / 88× 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 313 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-44231?
CVE-2026-44231 is a critical vulnerability published on July 20, 2026. RT is an open source, enterprise-grade issue and ticket tracking system. Versions prior to 5.0.10, 6.0.0 and above, prior to 6.0.3 contain an information disclosure and privilege escalation vulnerability in the REST 2.0 API. A privileged (non-administrative) user can obtain authentication…
When was CVE-2026-44231 disclosed?
CVE-2026-44231 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44231 actively exploited?
CVE-2026-44231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 67.4% of all scored CVEs.
What is the CVSS score of CVE-2026-44231?
CVE-2026-44231 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44231?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44231, 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-44231

Explore →

Is Your Infrastructure Affected by CVE-2026-44231?

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

Book a Demo →Browse All CVEs