CVE-2026-41073: bestpractical rt · CSV Injection
Affects bestpractical rtSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium : upgrade to 6.0.3 or 5.0.10 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.0.3, 5.0.10
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade rt and bestpractical/rt to 6.0.3 or 5.0.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bestpracticalrt | Affected
| Fixed in
|
| bestpracticalrt | Affected
| Fixed in
|
GitHubbestpractical/rtpkg:github/bestpractical/rtOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in bestpractical rt versions 5.0.10 and 6.0.3. Users should upgrade to these versions to fully remediate the vulnerability. If immediate upgrade is not possible, a temporary workaround is to avoid opening exported CSV files directly in spreadsheet applications when the data may contain untrusted user input.
Description
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.