VulertSecurity VulertSecurity

Vulnerability Database · Rocky Linux · Package report

glib2: vulnerability history, versions and safety

glib2 is a package in the Rocky Linux ecosystem. Vulert records 8 vulnerabilities for it across 8 affected ranges, from Sep 2024 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded U8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
6 in the last 12 months

Most recent disclosure 09 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all glib2 vulnerabilities

Vulert verdict on glib2 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 8 vulnerabilities on record across 1 year, 6 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 8 over 1 year · 6 in the last year i
  • Latest disclosure 09 Sep 2026 i
  • Highest CVSS 7.7 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.

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
up to 0:2.68.4-19.el9_8.10 (exclusive) 1
up to 0:2.68.4-19.el9_8.9 (exclusive) 1
up to 0:2.68.4-19.el9_8.2 (exclusive) 1
up to 0:2.68.4-19.el9_8.1 (exclusive) 1
up to 0:2.68.4-18.el9_7.2 (exclusive) 1
up to 0:2.68.4-18.el9_7.1 (exclusive) 1
up to 0:2.68.4-16.el9_6.2 (exclusive) 1
up to 0:2.68.4-14.el9_4.1 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2025 1
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for glib2

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Moderate Security Vulnerability in glib2: Integer Overflow in g_escape_uri_string() 7.7 high 0:2.68.4-18.el9_7.1 22 Jan 2026
Critical Integer Underflow Vulnerability in glib2 Package 7.5 high 0:2.68.4-19.el9_8.2 22 Jul 2026
Moderate Security Vulnerability in glib2: Multiple Buffer Over-Reads and Path Traversal Issues 7.3 high 0:2.68.4-19.el9_8.9 17 Aug 2026
Moderate Security Vulnerability in glib2: Heap-Based Buffer Overflow 7.1 high 0:2.68.4-19.el9_8.10 09 Sep 2026
Moderate Security Vulnerability in glib2: Buffer Overflow and Underflow Issues 7.0 high 0:2.68.4-16.el9_6.2 04 Oct 2025

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 glib2

Is glib2 safe to use?

Vulert records 8 vulnerabilities for glib2 in Rocky Linux: 0 critical, 0 high, 0 medium and 0 low, plus 8 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 glib2 have?

8 vulnerabilities are recorded for glib2 in the Rocky Linux ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 8 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 glib2 vulnerabilities disclosed?

6 vulnerabilities were recorded for glib2 in the last 12 months, and the oldest entry in this database dates to 17 Sep 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 glib2 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 glib2 for upcoming vulnerabilities?

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