Skip to content
Fencer Intel
low 2.6

CVE-2025-61873 json

Best Practical Request Tracker (RT) before 4.4.9, 5.0.9, and 6.0.2 allows CSV Injection via ticket values when TSV export is used.

published 9mo ago modified 4mo ago also EUVD-2026-2878

cvss
2.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

Best Practical Request Tracker (RT) before 4.4.9, 5.0.9, and 6.0.2 allows CSV Injection via ticket values when TSV export is used.

Patch / fix

  • bestpractical Request Tracker 4.4.9, 5.0.9, 6.0.2
  • request-tracker4 Debian 12 4.4.6+dfsg-1.1+deb12u3
  • request-tracker5 Debian 12 5.0.3+dfsg-3~deb12u4
  • request-tracker5 Debian 13 5.0.7+dfsg-4+deb13u1
  • request-tracker5 Debian 14 5.0.7+dfsg-5

debian advisories DEBIAN-CVE-2025-61873

Is CVE-2025-61873 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-61873 updated cvss 8.0

rt: CSV injection via ticket values when TSV export is used

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 2.6 CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:N/I:L/A:N

Affected products

  • bestpractical Request Tracker

Classification

Weakness
  • CWE-1236 Improper Neutralization of Formula Elements in a CSV File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.