CVE-2026-41073

MEDIUMNVD 4.64.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.6 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% 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, nvd
4.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.6Exploit: 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 and 6.0.0 through 6.0.2 contain a spreadsheet (CSV/formula) injection vulnerability. User-controlled data in spreadsheet exports is not sanitized before being written to the output file, which can cause spreadsheet applications to interpret crafted values as formulas or macros when the file is opened. 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 avoiding opening exported RT spreadsheet files directly in spreadsheet applications when the data may contain untrusted user input.

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

Published

May 22, 2026

Last Modified

July 23, 2026

Advisory Details (3)

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

Spreadsheet downloads vulnerable to CSV/formula injection in Microsoft Excel and similar apps · Advisory · bestpractical/rt · GitHub

https://github.com/bestpractical/rt/security/advisories/GHSA-6x92-7v65-7m3r
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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubunturt5-standalone (5.0.7+dfsg-6ubuntu0.1~esm1) @ resolute2026-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 6× in last 7d / 30× 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 173 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41073?
CVE-2026-41073 is a medium vulnerability published on May 22, 2026. RT is an open source, enterprise-grade issue and ticket tracking system. Versions prior to 5.0.10 and 6.0.0 through 6.0.2 contain a spreadsheet (CSV/formula) injection vulnerability. User-controlled data in spreadsheet exports is not sanitized before being written to the output file, which can…
When was CVE-2026-41073 disclosed?
CVE-2026-41073 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-41073 actively exploited?
CVE-2026-41073 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 93.8% of all scored CVEs.
What is the CVSS score of CVE-2026-41073?
CVE-2026-41073 has a CVSS v3 base score of 4.6 (NVD).
How do I remediate CVE-2026-41073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41073, 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-41073

Explore →

Is Your Infrastructure Affected by CVE-2026-41073?

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

Start Free Scan →Browse All CVEs