CVE-2026-58011

HIGHNVD 7.56.5▼
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-06-30. NVD baseline CVSS 7.5; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
6.5(high)
EPSS
26.4%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 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(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 26× 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.

  1. 2026-07-07 06:35 UTCEG score recompute
  2. 2026-07-07 06:34 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 07:39 UTCEG score recompute
  6. 2026-07-06 07:39 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 08:46 UTCEG score recompute
  10. 2026-07-05 08:46 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 09:56 UTCEG score recompute
  14. 2026-07-04 09:56 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 11:06 UTCEG score recompute
  18. 2026-07-03 11:06 UTCGHSA enrichment
  19. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-07-02 12:13 UTCEG score recompute
  21. 2026-07-02 12:13 UTCGHSA enrichment
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-07-01 13:23 UTCEG score recompute
  24. 2026-07-01 13:23 UTCGHSA enrichment
  25. 2026-06-30 14:34 UTCEG score recompute
Show 1 more
  1. 2026-06-30 14:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

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 July 2, 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 26.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58011?
CVE-2026-58011 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.5.
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

Explore the affected products and dependency analysis for 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