CVE-2026-58014

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% 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 — Patch released this weekElevated
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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
8.6(medium)
EG Risk
70(Attend)
EG Risk 70/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
Severity86% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 30, 2026

Last Modified

August 19, 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

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 45× in last 7d / 173× 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 252 total refreshes for this CVE.

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

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 August 19, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 74.1% of all scored CVEs.
What is the CVSS score of CVE-2026-58014?
CVE-2026-58014 has a CVSS v3 base score of 8.6 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by 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.