Linux
fort-validator security updates
Patch Radar has 39 security fixes for fort-validator, closing 13 CVEs. The newest security fix is DEBIAN-CVE-2026-53499 (1.6.8-1), released August 22, 2026.
Latest version
n/a
Release date not known
Security fixes
39
On record in Patch Radar
CVEs
13
Closed by those fixes
Exploited
0
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| Routine | DEBIAN-CVE-2026-53499 | Debian 14 | 1.6.8-1 | 1 | Aug 22, 2026 | |
| Routine | DEBIAN-CVE-2026-53499 | Debian 13.5 (trixie) | 1.6.8-0+deb13u1 | 1 | Aug 22, 2026 | |
| High | DLA-4066-1 | Debian 11.6 (bullseye) | 1.5.3-1~deb11u2 | 1 | Feb 24, 2025 | |
| Urgent | fort-validator 1.2.0-1ubuntu0.1~esm1 | Ubuntu 20.04 LTS (focal) | 1.2.0-1ubuntu0.1~esm1 | 7 | Jan 9, 2025 | |
| Urgent | fort-validator 1.5.3-1ubuntu0.1 | Ubuntu 22.04.1 LTS (jammy) | 1.5.3-1ubuntu0.1 | 7 | Jan 9, 2025 | |
| Urgent | fort-validator 1.6.1-1ubuntu0.1~esm2 | Ubuntu 24.04.5 LTS (noble) | 1.6.1-1ubuntu0.1~esm2 | 7 | Jan 9, 2025 | |
| High | DEBIAN-CVE-2024-56375 | Debian 13.5 (trixie) | 1.6.5-1 | 1 | Dec 22, 2024 | |
| High | DEBIAN-CVE-2024-56375 | Debian 14 | 1.6.5-1 | 1 | Dec 22, 2024 | |
| Urgent | DEBIAN-CVE-2024-45237 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| Urgent | DEBIAN-CVE-2024-45237 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| Urgent | DEBIAN-CVE-2024-45237 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45239 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45239 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45239 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45236 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45236 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45236 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45234 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45234 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45234 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45238 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45238 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45238 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45235 | Debian 12.15 (bookworm) | 1.5.4-1+deb12u1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45235 | Debian 13.5 (trixie) | 1.6.3-1 | 1 | Aug 24, 2024 | |
| High | DEBIAN-CVE-2024-45235 | Debian 14 | 1.6.3-1 | 1 | Aug 24, 2024 | |
| Urgent | DSA-5033-1 | Debian 11.6 (bullseye) | 1.5.3-1~deb11u1 | 1 | Dec 30, 2021 | |
| Urgent | DEBIAN-CVE-2021-3907 | Debian 12.15 (bookworm) | 1.5.3-1 | 1 | Nov 11, 2021 | |
| Urgent | DEBIAN-CVE-2021-3907 | Debian 13.5 (trixie) | 1.5.3-1 | 1 | Nov 11, 2021 | |
| Urgent | DEBIAN-CVE-2021-3907 | Debian 14 | 1.5.3-1 | 1 | Nov 11, 2021 | |
| High | DEBIAN-CVE-2021-3909 | Debian 12.15 (bookworm) | 1.5.3-1 | 1 | Nov 11, 2021 | |
| High | DEBIAN-CVE-2021-3909 | Debian 13.5 (trixie) | 1.5.3-1 | 1 | Nov 11, 2021 | |
| High | DEBIAN-CVE-2021-3909 | Debian 14 | 1.5.3-1 | 1 | Nov 11, 2021 | |
| High | DEBIAN-CVE-2021-43173 | Debian 12.15 (bookworm) | 1.5.3-1 | 1 | Nov 9, 2021 | |
| High | DEBIAN-CVE-2021-43173 | Debian 13.5 (trixie) | 1.5.3-1 | 1 | Nov 9, 2021 | |
| High | DEBIAN-CVE-2021-43173 | Debian 14 | 1.5.3-1 | 1 | Nov 9, 2021 | |
| High | DEBIAN-CVE-2021-43114 | Debian 12.15 (bookworm) | 1.5.2-1 | 1 | Nov 9, 2021 | |
| High | DEBIAN-CVE-2021-43114 | Debian 13.5 (trixie) | 1.5.2-1 | 1 | Nov 9, 2021 | |
| High | DEBIAN-CVE-2021-43114 | Debian 14 | 1.5.2-1 | 1 | Nov 9, 2021 |
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.