CVE-2026-44229

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 and 6.0.0 and above, prior to both 5.0.10 and 6.0.3 contain a Cross-Site Scripting (XSS) vulnerability where uploaded content is served inline rather than as an attachment. An authenticated user who can upload content can include JavaScript in the upload that will execute in the browser session of any RT user who later views or downloads it. This issue has been fixed in versions 5.0.10 and 6.0.3.

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

Published

July 20, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
Patch available. Sources: github_release, github.
github Patch Available

Cross-Site Scripting via inline-served uploaded content · Advisory · bestpractical/rt · GitHub

https://github.com/bestpractical/rt/security/advisories/GHSA-x576-pvwp-c2qv
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.7+dfsg-6ubuntu0.1~esm1) @ resolute2026-08-30ubuntu

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 13× in last 7d / 77× 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 102 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44229?
CVE-2026-44229 is a medium vulnerability published on July 20, 2026. RT is an open source, enterprise-grade issue and ticket tracking system. Versions 5.0.0 and 6.0.0 and above, prior to both 5.0.10 and 6.0.3 contain a Cross-Site Scripting (XSS) vulnerability where uploaded content is served inline rather than as an attachment. An authenticated user who can upload…
When was CVE-2026-44229 disclosed?
CVE-2026-44229 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44229 actively exploited?
CVE-2026-44229 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 85.1% of all scored CVEs.
What is the CVSS score of CVE-2026-44229?
CVE-2026-44229 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-44229?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44229, 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-44229

Explore →

Is Your Infrastructure Affected by CVE-2026-44229?

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

Start Free Scan →Browse All CVEs