VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

fort-validator: vulnerability history, versions and safety

fort-validator is a package in the Debian ecosystem. Vulert records 22 vulnerabilities for it across 22 releases, from Nov 2021 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
22 vulnerabilities recorded U22
i
5 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 21 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fort-validator vulnerabilities

Vulert verdict on fort-validator i

Updated on 23 Oct 2026

Careful: 5 of the 22 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 22 vulnerabilities on record across 4 years, 1 in the last year.

What to do: Plan around the 5 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 22 over 4 years · 1 in the last year i
  • Latest disclosure 21 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for fort-validator, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 22 of 22 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2024 16
  • 2025 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 22 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for fort-validator

The 5 most severe of 22 vulnerabilities recorded for this package

Search all 22 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Buffer Overflow Vulnerability in Fort Validator Package 9.8 critical 1.5.3-1~deb11u2 24 Aug 2024
Critical Crash Vulnerability in FORT Validator: Disabling Route Origin Validation 7.5 high 1.5.3-1~deb11u1 09 Nov 2021
Critical Panic Vulnerability in Fort Validator Package Leading to Route Origin Validation Unavailability 7.5 high 1.5.3-1~deb11u2 24 Aug 2024
Critical Null Pointer Dereference in Fort Validator (CVE-2024-45239) 7.5 high 1.5.3-1~deb11u2 24 Aug 2024
Critical Vulnerability in Fort Validator: Route Origin Validation Crash Risk 7.5 high 1.5.3-1~deb11u2 24 Aug 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About fort-validator

Is fort-validator safe to use?

Vulert records 22 vulnerabilities for fort-validator in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 22 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does fort-validator have?

22 vulnerabilities are recorded for fort-validator in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 22 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new fort-validator vulnerabilities disclosed?

1 vulnerability was recorded for fort-validator in the last 12 months, and the oldest entry in this database dates to 09 Nov 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of fort-validator are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor fort-validator for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the fort-validator version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.