CVE-2026-58011

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A flaw was found in GLib. An out-of-bounds read of only 2 bytes can occur in the g_date_time_get_ymd function in the glib/gdatetime.c file when an invalid GDateTime object produced by the g_date_time_add_full function is processed. This flaw can corrupt the date output and potentially cause logic errors that may lead to a denial of service.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

June 30, 2026

Last Modified

August 25, 2026

Advisory Details (4)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available

(#YWH-PGM9867-191) OOB Read on GLib through glib/gdatetime.c:g_date_time_get_ymd via invalid `GDateTime` (#3917) · Issues · GNOME / GLib · GitLab

https://gitlab.gnome.org/GNOME/glib/-/work_items/3917
generic🟡 PoC Available

(#YWH-PGM9867-191) OOB Read on GLib through glib/gdatetime.c:g_date_time_get_ymd via invalid `GDateTime` (#3917) · Issues · GNOME / GLib · GitLab

https://gitlab.gnome.org/GNOME/glib/-/issues/3917
redhat

2492245 – (CVE-2026-58011) CVE-2026-58011 glib: out-of-bounds read in glib/gdatetime.c:g_date_time_get_ymd via invalid GDateTime

https://bugzilla.redhat.com/show_bug.cgi?id=2492245
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-58011

Vendor Advisories for CVE-2026-58011(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatglib2-0:2.80.4-12.el10_2.212026-08-19redhat
redhatglib2-0:2.68.4-19.el9_8.92026-08-17redhat
redhatmingw-glib2-0:2.70.1-9.el8_102026-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
glib2.02.66.8-1 ... 2.89.3-2 (186 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glib2.02.74.6-2 ... 2.89.3-2 (139 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glib2.02.84.3-1 ... 2.89.3-2 (42 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glib2.02.84.3-1 ... 2.88.0-1 (35 versions)2.88.1-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 41× in last 7d / 182× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 256 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 10:22 UTCVendor advisory
  3. 2026-08-25 10:22 UTCGHSA enrichment
  4. 2026-08-25 09:57 UTCVendor advisory
  5. 2026-08-25 09:57 UTCGHSA enrichment
  6. 2026-08-24 23:10 UTCEG score recompute
  7. 2026-08-24 23:10 UTCVendor advisory
  8. 2026-08-24 23:10 UTCGHSA enrichment
  9. 2026-08-24 11:47 UTCEG score recompute
  10. 2026-08-24 11:47 UTCVendor advisory
  11. 2026-08-24 11:46 UTCGHSA enrichment
  12. 2026-08-23 19:50 UTCVendor advisory
  13. 2026-08-23 19:50 UTCGHSA enrichment
  14. 2026-08-23 08:27 UTCEG score recompute
  15. 2026-08-23 08:27 UTCVendor advisory
  16. 2026-08-23 08:27 UTCGHSA enrichment
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 20:39 UTCVendor advisory
  19. 2026-08-22 20:39 UTCGHSA enrichment
  20. 2026-08-22 08:29 UTCEG score recompute
  21. 2026-08-22 08:29 UTCVendor advisory
  22. 2026-08-22 08:29 UTCGHSA enrichment
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 17:20 UTCVendor advisory
  25. 2026-08-21 17:20 UTCGHSA enrichment
Show 75 more
  1. 2026-08-21 04:51 UTCEG score recompute
  2. 2026-08-21 04:51 UTCVendor advisory
  3. 2026-08-21 04:51 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 17:06 UTCVendor advisory
  6. 2026-08-20 17:06 UTCGHSA enrichment
  7. 2026-08-20 05:43 UTCVendor advisory
  8. 2026-08-20 05:43 UTCGHSA enrichment
  9. 2026-08-19 18:19 UTCVendor advisory
  10. 2026-08-19 18:19 UTCGHSA enrichment
  11. 2026-08-19 17:53 UTCEG score recompute
  12. 2026-08-19 17:53 UTCVendor advisory
  13. 2026-08-19 17:53 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 10:27 UTCVendor advisory
  16. 2026-08-19 10:27 UTCGHSA enrichment
  17. 2026-08-18 23:05 UTCEG score recompute
  18. 2026-08-18 23:05 UTCVendor advisory
  19. 2026-08-18 23:05 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-18 06:22 UTCEG score recompute
  22. 2026-08-18 06:22 UTCVendor advisory
  23. 2026-08-18 06:22 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 10:25 UTCVendor advisory
  26. 2026-08-17 10:25 UTCGHSA enrichment
  27. 2026-08-17 09:23 UTCVendor advisory
  28. 2026-08-17 09:23 UTCGHSA enrichment
  29. 2026-08-17 06:09 UTCVendor advisory
  30. 2026-08-17 06:09 UTCGHSA enrichment
  31. 2026-08-16 18:20 UTCEG score recompute
  32. 2026-08-16 18:20 UTCVendor advisory
  33. 2026-08-16 18:20 UTCGHSA enrichment
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 06:57 UTCEG score recompute
  36. 2026-08-16 06:57 UTCVendor advisory
  37. 2026-08-16 06:57 UTCGHSA enrichment
  38. 2026-08-16 02:14 UTCEPSS rescore
  39. 2026-08-15 19:35 UTCVendor advisory
  40. 2026-08-15 19:35 UTCGHSA enrichment
  41. 2026-08-15 08:09 UTCEG score recompute
  42. 2026-08-15 08:09 UTCVendor advisory
  43. 2026-08-15 08:09 UTCGHSA enrichment
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-14 19:41 UTCVendor advisory
  46. 2026-08-14 19:41 UTCGHSA enrichment
  47. 2026-08-14 08:19 UTCEG score recompute
  48. 2026-08-14 08:19 UTCVendor advisory
  49. 2026-08-14 08:19 UTCGHSA enrichment
  50. 2026-08-13 22:00 UTCEPSS rescore
  51. 2026-08-13 20:56 UTCVendor advisory
  52. 2026-08-13 20:56 UTCGHSA enrichment
  53. 2026-08-13 09:33 UTCVendor advisory
  54. 2026-08-13 09:33 UTCGHSA enrichment
  55. 2026-08-12 22:10 UTCEG score recompute
  56. 2026-08-12 22:10 UTCVendor advisory
  57. 2026-08-12 22:10 UTCGHSA enrichment
  58. 2026-08-12 13:51 UTCEPSS rescore
  59. 2026-08-12 10:48 UTCVendor advisory
  60. 2026-08-12 10:48 UTCGHSA enrichment
  61. 2026-08-11 23:25 UTCEG score recompute
  62. 2026-08-11 23:25 UTCVendor advisory
  63. 2026-08-11 23:25 UTCGHSA enrichment
  64. 2026-08-11 12:02 UTCVendor advisory
  65. 2026-08-11 12:02 UTCGHSA enrichment
  66. 2026-08-11 00:40 UTCEG score recompute
  67. 2026-08-11 00:40 UTCVendor advisory
  68. 2026-08-11 00:40 UTCGHSA enrichment
  69. 2026-08-11 00:00 UTCEPSS rescore
  70. 2026-08-10 13:17 UTCVendor advisory
  71. 2026-08-10 13:17 UTCGHSA enrichment
  72. 2026-08-10 01:55 UTCVendor advisory
  73. 2026-08-10 01:55 UTCGHSA enrichment
  74. 2026-08-09 14:32 UTCEG score recompute
  75. 2026-08-09 14:32 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-58011?
CVE-2026-58011 is a high vulnerability published on June 30, 2026. A flaw was found in GLib. An out-of-bounds read of only 2 bytes can occur in the gdatetimegetymd function in the glib/gdatetime.c file when an invalid GDateTime object produced by the gdatetimeaddfull function is processed. This flaw can corrupt the date output and potentially cause logic errors…
When was CVE-2026-58011 disclosed?
CVE-2026-58011 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58011 actively exploited?
CVE-2026-58011 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.6% of all scored CVEs.
What is the CVSS score of CVE-2026-58011?
CVE-2026-58011 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58011?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58011, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58011

Explore →

Is Your Infrastructure Affected by CVE-2026-58011?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs