Vulert records 14 vulnerabilities for glib in OSS-Fuzz: 0 critical, 1 high, 12 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.

How many vulnerabilities does glib have?

14 vulnerabilities are recorded for glib in the OSS-Fuzz ecosystem: 0 critical, 1 high, 12 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?

1 vulnerability was recorded for glib in the last 12 months, and the oldest entry in this database dates to 01 Jul 2020. 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 https://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.

Vulnerability Database · OSS-Fuzz · Package report

glib: vulnerability history, versions and safety

glib is a package in the OSS-Fuzz ecosystem. Vulert records 14 vulnerabilities for it across 12 releases, from Jul 2020 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

14 vulnerabilities recorded H1 M12 U1

0 with no fix published

Every vulnerability has a patched version to move to.

1 in the last 12 months

Most recent disclosure 03 Apr 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all glib vulnerabilities

Vulert verdict on glib i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 03 Apr 2026. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 14 vulnerabilities on record across 5 years, 1 in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

Vulnerabilities on record 14 over 5 years · 1 in the last year i
Latest disclosure 03 Apr 2026 i
Highest CVSS n/a i
With no published fix 0 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert holds for glib, 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.

Version	Vulert vulnerabilities	Fix published	Details
2.66.0	M1	Yes	Details →
2.65.3	M1	Yes	Details →
2.65.2	M1	Yes	Details →
2.65.1	M1	Yes	Details →
2.62.0	M1	Yes	Details →
2.61.3	M1	Yes	Details →
2.61.2	M1	Yes	Details →
2.58.3	M6	Yes	Details →
2.58.2	M6	Yes	Details →
2.58.1	M6	Yes	Details →
2.58.0	M6	Yes	Details →
2.57.3	M8	Yes	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2020 5
2021 8
2026 1

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for glib

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
Heap-buffer-overflow in glib: uri_decoder	N/A medium	15bf2ddaf5cfae484f714ebb9f0895a79959f29e	04 Jul 2020
Global-buffer-overflow in g_date_time_get_ymd in glib	N/A unrated	c3805d74ba4c46aacf9470646fdecdcba68e11d0	10 Dec 2020
Use-of-uninitialized-value in g_date_time_get_week_number in glib	N/A medium	f4dd85628af916b58aaead3e8dd25d14d1a7cb95	01 Jul 2020
Heap-buffer-overflow in uri_decoder in glib	N/A medium	f9d165add1342ecae6cdde1b95e9ce63320768dd	04 Jul 2020
Use-of-uninitialized-value in g_dbus_message_new_from_blob	N/A medium	d192a078c876107652e535e3e74b90e387d51a0f	13 Jan 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