CVE-2026-58013

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 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 — Patch released this week
8.2EG
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.2Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in GLib. A buffer over-read can occur in g_io_channel_read_line_backend() in the giochannel.c file when a custom line terminator with a length greater than one is set, causing memcmp to read past the GString buffer. This vulnerability can cause a minor information disclosure of 7 bytes or a denial of service when the buffer over-read crosses a page boundary.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
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-199) Buffer Over-read on GLib through glib/giochannel.c via "g_io_channel_read_line_backend" (#3925) · Issues · GNOME / GLib · GitLab

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

2492248 – (CVE-2026-58013) CVE-2026-58013 glib: buffer over-read in glib/giochannel.c via "g_io_channel_read_line_backend"

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

cve-details

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

Vendor Advisories for CVE-2026-58013(5)

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 48× in last 7d / 170× 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 226 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-58013?
CVE-2026-58013 is a high vulnerability published on June 30, 2026. A flaw was found in GLib. A buffer over-read can occur in giochannelreadline_backend() in the giochannel.c file when a custom line terminator with a length greater than one is set, causing memcmp to read past the GString buffer. This vulnerability can cause a minor information disclosure of 7 bytes…
When was CVE-2026-58013 disclosed?
CVE-2026-58013 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-58013 actively exploited?
CVE-2026-58013 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.7% of all scored CVEs.
What is the CVSS score of CVE-2026-58013?
CVE-2026-58013 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-58013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58013, 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-58013

Explore →

Is Your Infrastructure Affected by CVE-2026-58013?

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

Start Free Scan →Browse All CVEs