VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

glib: vulnerability history, versions and safety

glib is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 46 releases, from Mar 2024 to Dec 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
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 glib vulnerabilities

Vulert verdict on glib 0.22.10 i

Updated on 23 Oct 2026

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

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 0.22.10 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 23 Dec 2024 i
  • Highest CVSS 6.9 i
  • With no published fix 0 i
  • Stars 377 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month ago i
  • Licence MIT i
  • Similar names glob 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 glib, 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
0.22.10 19 Sep 2026 none MIT — Details →
0.22.9 30 Aug 2026 none MIT — Details →
0.22.8 29 Jun 2026 none MIT — Details →
0.22.7 29 Apr 2026 none MIT — Details →
0.22.6 27 Apr 2026 none MIT — Details →
0.22.5 12 Apr 2026 none MIT — Details →
0.22.4 05 Apr 2026 none MIT — Details →
0.22.3 14 Mar 2026 none MIT — Details →
0.22.2 28 Feb 2026 none MIT — Details →
0.22.0 20 Feb 2026 none MIT — Details →
0.22.0-alpha.3 05 Feb 2026 none MIT — Details →
0.22.0-alpha.2 10 Jan 2026 none MIT — Details →
0.22.0-alpha.1 01 Jan 2026 none MIT — Details →
0.21.5 02 Dec 2025 none MIT — Details →
0.21.4 30 Oct 2025 none MIT — Details →
0.21.3 21 Sep 2025 none MIT — Details →
0.21.2 17 Sep 2025 none MIT — Details →
0.21.1 09 Aug 2025 none MIT — Details →
0.21.0 15 Jul 2025 none MIT — Details →
0.20.12 20 Jun 2025 none MIT — Details →
0.20.10 13 May 2025 none MIT — Details →
0.20.9 16 Feb 2025 none MIT — Details →
0.20.7 16 Dec 2024 none MIT — Details →
0.20.6 12 Nov 2024 none MIT — Details →
0.20.5 30 Oct 2024 none MIT — Details →
0.20.4 26 Sep 2024 none MIT — Details →
0.20.3 09 Sep 2024 none MIT — Details →
0.20.2 27 Aug 2024 none MIT — Details →
0.20.1 12 Aug 2024 none MIT — Details →
0.20.0 10 Jul 2024 none MIT — Details →
0.19.9 26 Jun 2024 M1 U1 MIT Yes Details →
0.19.8 19 Jun 2024 M1 U1 MIT Yes Details →
0.19.7 23 May 2024 M1 U1 MIT Yes Details →
0.19.6 10 May 2024 M1 U1 MIT Yes Details →
0.19.5 27 Apr 2024 M1 U1 MIT Yes Details →
0.19.4 08 Apr 2024 M1 U1 MIT Yes Details →
0.19.3 19 Mar 2024 M1 U1 MIT Yes Details →
0.19.2 13 Feb 2024 M1 U1 MIT Yes Details →
0.19.0 04 Feb 2024 M1 U1 MIT Yes Details →
0.18.5 30 Dec 2023 M1 U1 MIT Yes Details →
0.18.4 09 Dec 2023 M1 U1 MIT Yes Details →
0.18.3 03 Nov 2023 M1 U1 MIT Yes Details →
0.18.2 14 Sep 2023 M1 U1 MIT Yes Details →
0.18.1 01 Aug 2023 M1 U1 MIT Yes Details →
0.18.0 23 Jul 2023 M1 U1 MIT Yes Details →
0.16.9 06 Jun 2023 M1 U1 MIT Yes Details →
0.17.10 06 Jun 2023 M1 U1 MIT Yes Details →
0.17.9 21 Apr 2023 M1 U1 MIT Yes Details →
0.17.8 13 Apr 2023 M1 U1 MIT Yes Details →
0.17.5 15 Mar 2023 M1 U1 MIT Yes Details →
0.17.4 14 Mar 2023 M1 U1 MIT Yes Details →
0.17.3 06 Mar 2023 M1 U1 MIT Yes Details →
0.17.2 21 Feb 2023 M1 U1 MIT Yes Details →
0.17.1 13 Feb 2023 M1 U1 MIT Yes Details →
0.17.0 08 Feb 2023 M1 U1 MIT Yes Details →
0.16.7 16 Dec 2022 M1 U1 MIT Yes Details →
0.16.6 12 Dec 2022 M1 U1 MIT Yes Details →
0.16.5 05 Dec 2022 M1 U1 MIT Yes Details →
0.16.4 28 Nov 2022 M1 U1 MIT Yes Details →
0.16.3 13 Nov 2022 M1 U1 MIT Yes Details →
0.16.2 23 Oct 2022 M1 U1 MIT Yes Details →
0.16.1 21 Oct 2022 M1 U1 MIT Yes Details →
0.16.0 19 Oct 2022 M1 U1 MIT Yes Details →
0.15.12 27 Jun 2022 M1 U1 MIT Yes Details →
0.15.11 26 Apr 2022 M1 U1 MIT Yes Details →
0.15.10 19 Mar 2022 M1 U1 MIT Yes Details →
0.15.9 10 Mar 2022 M1 U1 MIT Yes Details →
0.15.8 08 Mar 2022 M1 U1 MIT Yes Details →
0.15.7 08 Mar 2022 M1 U1 MIT Yes Details →
0.15.6 20 Feb 2022 M1 U1 MIT Yes Details →
0.15.5 06 Feb 2022 M1 U1 MIT Yes Details →
0.15.4 31 Jan 2022 M1 U1 MIT Yes Details →
0.15.3 24 Jan 2022 M1 U1 MIT Yes Details →
0.15.2 16 Jan 2022 M1 U1 MIT Yes Details →
0.15.1 15 Jan 2022 M1 U1 MIT Yes Details →
0.15.0 14 Jan 2022 M1 U1 MIT Yes Details →
0.14.8 09 Oct 2021 none MIT — Details →
0.14.5 31 Aug 2021 none MIT — Details →
0.14.4 23 Aug 2021 none MIT — Details →
0.14.3 23 Aug 2021 none MIT — Details →
0.14.2 09 Jul 2021 none MIT — Details →
0.14.1 08 Jul 2021 none MIT — Details →
0.14.0 22 Jun 2021 none MIT — Details →
0.10.3 14 Oct 2020 none MIT — Details →
0.10.2 10 Sep 2020 none MIT — Details →
0.10.1 07 Jul 2020 none MIT — Details →
0.10.0 04 Jul 2020 none MIT — Details →
0.9.3 14 Feb 2020 none MIT — Details →
0.9.2 07 Feb 2020 none MIT — Details →
0.9.1 12 Jan 2020 none MIT — Details →
0.9.0 14 Dec 2019 none MIT — Details →
0.8.2 23 Sep 2019 none MIT — Details →
0.8.1 17 Jul 2019 none MIT — Details →
0.8.0 22 Jun 2019 none MIT — Details →
0.7.1 25 Feb 2019 none MIT — Details →
0.7.0 21 Feb 2019 none MIT — Details →
0.6.1 14 Dec 2018 none MIT — Details →
0.6.0 09 Sep 2018 none MIT — Details →
0.5.0 17 Mar 2018 none MIT — Details →
0.4.1 20 Jan 2018 none MIT — Details →
0.4.0 26 Nov 2017 none — — Details →
0.3.1 26 Aug 2017 none — — Details →
0.3.0 20 Aug 2017 none — — Details →
0.1.3 06 May 2017 none — — Details →
0.1.2 04 Mar 2017 none — — Details →
0.1.1 27 Nov 2016 none — — Details →
0.1.0 14 Jun 2016 none — — Details →
0.0.8 15 Mar 2016 none — — Details →
0.0.7 27 Nov 2015 none — — Details →
0.0.6 27 Nov 2015 none — — Details →
0.0.5 20 Oct 2015 none — — Details →
0.0.4 09 Sep 2015 none — — Details →
0.0.3 18 Jul 2015 none — — Details →
0.0.2 24 May 2015 none — — Details →
0.0.1 12 May 2015 none — — Details →

All 115 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for glib

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unsoundness in Iterator Implementations in glib Package: A Critical Vulnerability 6.9 medium 0.20.0 23 Dec 2024
Unsoundness in glib Package: Iterator and DoubleEndedIterator Implementations Vulnerability N/A unrated 0.20.0 30 Mar 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 glib

Is glib safe to use?

Vulert records 2 vulnerabilities for glib in crates.io: 0 critical, 0 high, 1 medium and 0 low, plus 1 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 glib's Vulert package health score?

Vulert scores glib 73/100, which reads as in good shape. 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 glib affected?

No. 0.22.10, 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 glib should I use?

0.22.10 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 glib have?

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

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

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