[request-tracker-maintainers] Bug#1152514: request-tracker5: CVE-2026-105454 CVE-2026-108270 CVE-2026-108271 CVE-2026-108272 CVE-2026-108273 CVE-2026-108274 CVE-2026-108275 CVE-2026-108276 CVE-2026-108277 CVE-2026-108278 CVE-2026-108279 CVE-2026-108280 CVE-2026-108281 CVE-2026-108282 CVE-2026-108342 CVE-2026-108343 CVE-2026-108344 CVE-2026-108346 CVE-2026-108347 CVE-2026-108348 CVE-2026-108349 CVE-2026-108350 CVE-2026-108351 CVE-2026-108352 CVE-2026-108353 CVE-2026-108363 CVE-2026-108365 CVE-2026-108371

Salvatore Bonaccorso carnil at debian.org
Fri Oct 30 04:42:16 GMT 2026


Source: request-tracker5
Version: 5.0.10+dfsg-3
X-Debbugs-CC: team at security.debian.org
Severity: grave
Tags: security upstream

Hi,

The following vulnerabilities were published for request-tracker5.

CVE-2026-105454[0], CVE-2026-108270[1], CVE-2026-108271[2],
CVE-2026-108272[3], CVE-2026-108273[4], CVE-2026-108274[5],
CVE-2026-108275[6], CVE-2026-108276[7], CVE-2026-108277[8],
CVE-2026-108278[9], CVE-2026-108279[10], CVE-2026-108280[11],
CVE-2026-108281[12], CVE-2026-108282[13], CVE-2026-108342[14],
CVE-2026-108343[15], CVE-2026-108344[16], CVE-2026-108346[17],
CVE-2026-108347[18], CVE-2026-108348[19], CVE-2026-108349[20],
CVE-2026-108350[21], CVE-2026-108351[22], CVE-2026-108352[23],
CVE-2026-108353[24], CVE-2026-108363[25], CVE-2026-108365[26],
CVE-2026-108371[27].

Due to the amount of CVEs we have not yet tracked down the needed
fixes from the repository to address the individual CVEs.

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-105454
    https://www.cve.org/CVERecord?id=CVE-2026-105454
[1] https://security-tracker.debian.org/tracker/CVE-2026-108270
    https://www.cve.org/CVERecord?id=CVE-2026-108270
[2] https://security-tracker.debian.org/tracker/CVE-2026-108271
    https://www.cve.org/CVERecord?id=CVE-2026-108271
[3] https://security-tracker.debian.org/tracker/CVE-2026-108272
    https://www.cve.org/CVERecord?id=CVE-2026-108272
[4] https://security-tracker.debian.org/tracker/CVE-2026-108273
    https://www.cve.org/CVERecord?id=CVE-2026-108273
[5] https://security-tracker.debian.org/tracker/CVE-2026-108274
    https://www.cve.org/CVERecord?id=CVE-2026-108274
[6] https://security-tracker.debian.org/tracker/CVE-2026-108275
    https://www.cve.org/CVERecord?id=CVE-2026-108275
[7] https://security-tracker.debian.org/tracker/CVE-2026-108276
    https://www.cve.org/CVERecord?id=CVE-2026-108276
[8] https://security-tracker.debian.org/tracker/CVE-2026-108277
    https://www.cve.org/CVERecord?id=CVE-2026-108277
[9] https://security-tracker.debian.org/tracker/CVE-2026-108278
    https://www.cve.org/CVERecord?id=CVE-2026-108278
[10] https://security-tracker.debian.org/tracker/CVE-2026-108279
    https://www.cve.org/CVERecord?id=CVE-2026-108279
[11] https://security-tracker.debian.org/tracker/CVE-2026-108280
    https://www.cve.org/CVERecord?id=CVE-2026-108280
[12] https://security-tracker.debian.org/tracker/CVE-2026-108281
    https://www.cve.org/CVERecord?id=CVE-2026-108281
[13] https://security-tracker.debian.org/tracker/CVE-2026-108282
    https://www.cve.org/CVERecord?id=CVE-2026-108282
[14] https://security-tracker.debian.org/tracker/CVE-2026-108342
    https://www.cve.org/CVERecord?id=CVE-2026-108342
[15] https://security-tracker.debian.org/tracker/CVE-2026-108343
    https://www.cve.org/CVERecord?id=CVE-2026-108343
[16] https://security-tracker.debian.org/tracker/CVE-2026-108344
    https://www.cve.org/CVERecord?id=CVE-2026-108344
[17] https://security-tracker.debian.org/tracker/CVE-2026-108346
    https://www.cve.org/CVERecord?id=CVE-2026-108346
[18] https://security-tracker.debian.org/tracker/CVE-2026-108347
    https://www.cve.org/CVERecord?id=CVE-2026-108347
[19] https://security-tracker.debian.org/tracker/CVE-2026-108348
    https://www.cve.org/CVERecord?id=CVE-2026-108348
[20] https://security-tracker.debian.org/tracker/CVE-2026-108349
    https://www.cve.org/CVERecord?id=CVE-2026-108349
[21] https://security-tracker.debian.org/tracker/CVE-2026-108350
    https://www.cve.org/CVERecord?id=CVE-2026-108350
[22] https://security-tracker.debian.org/tracker/CVE-2026-108351
    https://www.cve.org/CVERecord?id=CVE-2026-108351
[23] https://security-tracker.debian.org/tracker/CVE-2026-108352
    https://www.cve.org/CVERecord?id=CVE-2026-108352
[24] https://security-tracker.debian.org/tracker/CVE-2026-108353
    https://www.cve.org/CVERecord?id=CVE-2026-108353
[25] https://security-tracker.debian.org/tracker/CVE-2026-108363
    https://www.cve.org/CVERecord?id=CVE-2026-108363
[26] https://security-tracker.debian.org/tracker/CVE-2026-108365
    https://www.cve.org/CVERecord?id=CVE-2026-108365
[27] https://security-tracker.debian.org/tracker/CVE-2026-108371
    https://www.cve.org/CVERecord?id=CVE-2026-108371
[28] https://github.com/bestpractical/rt/releases/tag/rt-5.0.11

Regards,
Salvatore



More information about the pkg-request-tracker-maintainers mailing list