VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

fltk: vulnerability history, versions and safety

fltk is a package in the crates.io ecosystem. Vulert records 5 vulnerabilities for it across 0 release, from Mar 2021 to Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded C1 H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all fltk vulnerabilities

Vulert verdict on fltk 1.5.23 i

Updated on 23 Oct 2026

Good news: 1.5.23, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 69/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 1.5.23 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.5.23 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.5.23 — unaffected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 54 packages i
  • Stars 1,862 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for fltk, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.5.23 03 May 2026 none MIT — Details →
1.5.22 16 Nov 2025 none MIT — Details →
1.5.21 30 Oct 2025 none MIT — Details →
1.5.20 20 Oct 2025 none MIT — Details →
1.5.19 16 Oct 2025 none MIT — Details →
1.5.18 16 Oct 2025 none MIT — Details →
1.5.17 02 Oct 2025 none MIT — Details →
1.5.16 02 Oct 2025 none MIT — Details →
1.5.15 29 Sep 2025 none MIT — Details →
1.5.14 04 Sep 2025 none MIT — Details →
1.5.13 18 Aug 2025 none MIT — Details →
1.5.12 18 Aug 2025 none MIT — Details →
1.5.11 17 Aug 2025 none MIT — Details →
1.5.10 26 Jul 2025 none MIT — Details →
1.5.9 21 May 2025 none MIT — Details →
1.5.8 08 May 2025 none MIT — Details →
1.5.7 15 Apr 2025 none MIT — Details →
1.5.6 01 Apr 2025 none MIT — Details →
1.5.5 23 Mar 2025 none MIT — Details →
1.5.4 22 Feb 2025 none MIT — Details →
1.5.3 04 Feb 2025 none MIT — Details →
1.5.2 11 Jan 2025 none MIT — Details →
1.5.1 10 Dec 2024 none MIT — Details →
1.5.0 08 Dec 2024 none MIT — Details →
1.4.36 13 Nov 2024 none MIT — Details →
1.4.35 21 Oct 2024 none MIT — Details →
1.4.34 24 Sep 2024 none MIT — Details →
1.4.33 30 Jul 2024 none MIT — Details →
1.4.32 20 Jun 2024 none MIT — Details →
1.4.31 07 Jun 2024 none MIT — Details →
1.4.30 08 May 2024 none MIT — Details →
1.4.29 23 Apr 2024 none MIT — Details →
1.4.28 04 Apr 2024 none MIT — Details →
1.4.27 31 Mar 2024 none MIT — Details →
1.4.26 09 Mar 2024 none MIT — Details →
1.4.25 21 Feb 2024 none MIT — Details →
1.4.24 30 Jan 2024 none MIT — Details →
1.4.23 28 Jan 2024 none MIT — Details →
1.4.22 14 Jan 2024 none MIT — Details →
1.4.21 30 Dec 2023 none MIT — Details →
1.4.20 16 Dec 2023 none MIT — Details →
1.4.19 03 Dec 2023 none MIT — Details →
1.4.18 17 Nov 2023 none MIT — Details →
1.4.17 16 Nov 2023 none MIT — Details →
1.4.16 02 Nov 2023 none MIT — Details →
1.4.15 20 Oct 2023 none MIT — Details →
1.4.14 08 Oct 2023 none MIT — Details →
1.4.13 23 Sep 2023 none MIT — Details →
1.4.12 09 Sep 2023 none MIT — Details →
1.4.11 05 Sep 2023 none MIT — Details →
1.4.10 23 Aug 2023 none MIT — Details →
1.4.9 30 Jul 2023 none MIT — Details →
1.4.8 19 Jul 2023 none MIT — Details →
1.4.7 04 Jul 2023 none MIT — Details →
1.4.6 27 Jun 2023 none MIT — Details →
1.4.5 08 Jun 2023 none MIT — Details →
1.4.4 22 May 2023 none MIT — Details →
1.4.3 08 May 2023 none MIT — Details →
1.4.2 27 Apr 2023 none MIT — Details →
1.4.1 13 Apr 2023 none MIT — Details →
1.4.0 31 Mar 2023 none MIT — Details →
1.3.34 19 Mar 2023 none MIT — Details →
1.3.33 08 Mar 2023 none MIT — Details →
1.3.32 02 Mar 2023 none MIT — Details →
1.3.31 16 Feb 2023 none MIT — Details →
1.3.30 07 Feb 2023 none MIT — Details →
1.3.29 02 Feb 2023 none MIT — Details →
1.3.28 23 Jan 2023 none MIT — Details →
1.3.27 13 Jan 2023 none MIT — Details →
1.3.26 05 Jan 2023 none MIT — Details →
1.3.25 24 Dec 2022 none MIT — Details →
1.3.24 15 Dec 2022 none MIT — Details →
1.3.23 02 Dec 2022 none MIT — Details →
1.3.22 01 Dec 2022 none MIT — Details →
1.3.21 24 Nov 2022 none MIT — Details →
1.3.20 13 Nov 2022 none MIT — Details →
1.3.19 31 Oct 2022 none MIT — Details →
1.3.18 21 Oct 2022 none MIT — Details →
1.3.17 21 Oct 2022 none MIT — Details →
1.3.16 05 Oct 2022 none MIT — Details →
1.3.15 11 Sep 2022 none MIT — Details →
1.3.14 06 Sep 2022 none MIT — Details →
1.3.13 09 Aug 2022 none MIT — Details →
1.3.12 25 Jul 2022 none MIT — Details →
1.3.11 10 Jul 2022 none MIT — Details →
1.3.10 30 Jun 2022 none MIT — Details →
1.3.9 23 Jun 2022 none MIT — Details →
1.3.8 06 Jun 2022 none MIT — Details →
1.3.7 19 May 2022 none MIT — Details →
1.3.6 22 Apr 2022 none MIT — Details →
1.3.5 16 Apr 2022 none MIT — Details →
1.3.4 10 Apr 2022 none MIT — Details →
1.3.3 10 Apr 2022 none MIT — Details →
1.3.2 31 Mar 2022 none MIT — Details →
1.3.1 22 Mar 2022 none MIT — Details →
1.3.0 06 Mar 2022 none MIT — Details →
1.2.32 26 Feb 2022 none MIT — Details →
1.2.31 19 Feb 2022 none MIT — Details →
1.2.30 10 Feb 2022 none MIT — Details →
1.2.29 31 Jan 2022 none MIT — Details →
1.2.28 22 Jan 2022 none — — Details →
1.2.27 14 Jan 2022 none — — Details →
1.2.26 05 Jan 2022 none — — Details →
1.2.25 30 Dec 2021 none — — Details →
1.2.24 26 Dec 2021 none — — Details →
1.2.23 21 Dec 2021 none — — Details →
1.2.22 19 Dec 2021 none — — Details →
1.2.21 13 Dec 2021 none — — Details →
1.2.20 08 Dec 2021 none — — Details →
1.2.19 03 Dec 2021 none — — Details →
1.2.18 27 Nov 2021 none — — Details →
1.2.17 21 Nov 2021 none — — Details →
1.2.16 14 Nov 2021 none — — Details →
1.2.15 10 Nov 2021 none — — Details →
1.2.14 08 Nov 2021 none — — Details →
1.2.13 01 Nov 2021 none — — Details →
1.2.12 30 Oct 2021 none — — Details →
1.2.11 30 Oct 2021 none — — Details →
1.2.10 23 Oct 2021 none — — Details →
1.2.9 19 Oct 2021 none — — Details →

The newest 120 of 401 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 5

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

03 Vulnerabilities

Recorded vulnerabilities for fltk

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-28308: Out of Bounds Read in fltk 9.1 critical 0.15.3 25 Aug 2021
CVE-2021-28307: Null pointer dereference in fltk 7.5 high 0.15.3 25 Aug 2021
CVE-2021-28306: Null pointer dereference in fltk crate 7.5 high 0.15.3 25 Aug 2021
CVE-2021-28306: Null pointer dereference in fltk crate before 0.15.3 for Rust N/A unrated 0.15.3 06 Mar 2021
CVE-2021-28306: fltk - Multiple memory safety issues N/A unrated 0.15.3 06 Mar 2021

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 fltk

Is fltk safe to use?

Vulert records 5 vulnerabilities for fltk in crates.io: 1 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is fltk's Vulert package health score?

Vulert scores fltk 69/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of fltk affected?

No. 1.5.23, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of fltk should I use?

1.5.23 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does fltk have?

5 vulnerabilities are recorded for fltk in the crates.io ecosystem: 1 critical, 2 high, 0 medium and 0 low, plus 2 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 fltk vulnerabilities disclosed?

0 vulnerabilities were recorded for fltk in the last 12 months, and the oldest entry in this database dates to 06 Mar 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 fltk 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 fltk for upcoming vulnerabilities?

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