CVE-2026-58014

HIGHNVD 8.67.3▼
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. NVD baseline CVSS 8.6; sources differ by 1.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: 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 off-by-one error can occur in the g_key_file_get_locale_string_list function in the gkeyfile.c file when loading a key file with an empty value. This flaw can cause an out-of-bounds access of 1 byte or a denial of service when the out-of-bounds access crosses a page boundary.

CVSS v3
8.6
EG Score
7.3(medium)
EG Risk
—
EPSS
21.4%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 1, 2026

Advisory Details (3)

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

(#YWH-PGM9867-200) Off-by-one Error on GLib through glib/gkeyfile.c via "g_key_file_get_locale_string_list" (#3930) · Issues · GNOME / GLib · GitLab

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

2492255 – (CVE-2026-58014) CVE-2026-58014 glib: off-by-one error in glib/gkeyfile.c via "g_key_file_get_locale_string_list"

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

cve-details

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

Vendor Advisories for CVE-2026-58014(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 13× in last 7d / 81× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 20:25 UTCVendor advisory
  10. 2026-07-16 20:25 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 09:18 UTCVendor advisory
  13. 2026-07-16 09:18 UTCGHSA enrichment
  14. 2026-07-15 22:11 UTCVendor advisory
  15. 2026-07-15 22:11 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 10:55 UTCVendor advisory
  19. 2026-07-15 10:55 UTCGHSA enrichment
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 23:45 UTCVendor advisory
  23. 2026-07-14 23:45 UTCGHSA enrichment
  24. 2026-07-14 12:38 UTCVendor advisory
  25. 2026-07-14 12:38 UTCGHSA enrichment
Show 56 more
  1. 2026-07-14 01:32 UTCVendor advisory
  2. 2026-07-14 01:32 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 14:26 UTCGHSA enrichment
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 03:16 UTCVendor advisory
  8. 2026-07-13 03:15 UTCGHSA enrichment
  9. 2026-07-12 16:02 UTCVendor advisory
  10. 2026-07-12 16:01 UTCGHSA enrichment
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-12 04:54 UTCVendor advisory
  13. 2026-07-12 04:54 UTCGHSA enrichment
  14. 2026-07-11 17:47 UTCVendor advisory
  15. 2026-07-11 17:47 UTCGHSA enrichment
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 06:40 UTCGHSA enrichment
  19. 2026-07-10 19:33 UTCGHSA enrichment
  20. 2026-07-10 08:27 UTCGHSA enrichment
  21. 2026-07-09 21:15 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 10:09 UTCGHSA enrichment
  25. 2026-07-08 23:02 UTCGHSA enrichment
  26. 2026-07-08 15:16 UTCEPSS rescore
  27. 2026-07-08 15:16 UTCEPSS rescore
  28. 2026-07-08 11:54 UTCGHSA enrichment
  29. 2026-07-08 00:30 UTCGHSA enrichment
  30. 2026-07-07 13:46 UTCEPSS rescore
  31. 2026-07-07 13:46 UTCEPSS rescore
  32. 2026-07-07 13:23 UTCGHSA enrichment
  33. 2026-07-07 02:16 UTCGHSA enrichment
  34. 2026-07-06 16:27 UTCEPSS rescore
  35. 2026-07-06 16:27 UTCEPSS rescore
  36. 2026-07-06 15:07 UTCGHSA enrichment
  37. 2026-07-06 03:59 UTCGHSA enrichment
  38. 2026-07-06 02:23 UTCEPSS rescore
  39. 2026-07-06 02:23 UTCEPSS rescore
  40. 2026-07-05 16:53 UTCGHSA enrichment
  41. 2026-07-05 05:45 UTCGHSA enrichment
  42. 2026-07-05 02:31 UTCEPSS rescore
  43. 2026-07-05 02:30 UTCEPSS rescore
  44. 2026-07-04 18:37 UTCGHSA enrichment
  45. 2026-07-04 07:28 UTCGHSA enrichment
  46. 2026-07-03 20:21 UTCGHSA enrichment
  47. 2026-07-03 09:14 UTCGHSA enrichment
  48. 2026-07-02 22:07 UTCGHSA enrichment
  49. 2026-07-02 11:00 UTCGHSA enrichment
  50. 2026-07-01 23:53 UTCGHSA enrichment
  51. 2026-07-01 19:07 UTCNVD updateCVSS v3 → 8.6
  52. 2026-07-01 15:07 UTCEPSS rescore
  53. 2026-07-01 12:46 UTCGHSA enrichment
  54. 2026-07-01 01:40 UTCGHSA enrichment
  55. 2026-06-30 14:33 UTCEG score recompute
  56. 2026-06-30 14:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-58014?
CVE-2026-58014 is a high vulnerability published on June 30, 2026. A flaw was found in GLib. An off-by-one error can occur in the gkeyfilegetlocalestringlist function in the gkeyfile.c file when loading a key file with an empty value. This flaw can cause an out-of-bounds access of 1 byte or a denial of service when the out-of-bounds access crosses a page boundary.
When was CVE-2026-58014 disclosed?
CVE-2026-58014 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58014 actively exploited?
CVE-2026-58014 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58014?
CVE-2026-58014 has a CVSS v3 base score of 8.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.3.
How do I remediate CVE-2026-58014?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58014, 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-58014

Explore →

Is Your Infrastructure Affected by CVE-2026-58014?

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

Start Free Scan →Browse All CVEs