Out-of-bounds read in GLib g_date_time_get_ymd

Successful exploitation can cause corrupted date values to be returned to the application, which may in turn trigger logic faults and denial-of-service conditions. Based on the available information, the primary security impact is availability degradation through application instability or failure caused by malformed date handling rather than direct code execution or privilege escalation.

Until patched packages can be deployed, reduce exposure by avoiding or strictly validating code paths that create or process GDateTime objects derived from g_date_time_add_full when inputs may be invalid or attacker-influenced. Applications should defensively validate date/time objects before passing them to g_date_time_get_ymd and handle anomalous date computation results safely to prevent crashes or logic failures. Complete mitigation information beyond patching is currently not available.

Apply vendor-provided GLib/glib2 security updates that include the fix for CVE-2026-58011. Reported fixed package streams include Red Hat updates for mingw-glib2 2.70.1-9.el8_10, glib2 2.68.4-19.el9_8.9, and glib2 2.80.4-12.el10_2.21, as distributed through the relevant platform advisories. Systems using downstream rebuilds should install the corresponding patched packages from their vendor.