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.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
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: 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. 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
42(Track)
EG Risk 42/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
25.3%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 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(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 11× in last 7d / 61× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute▲ 1.70
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 14:56 UTCVendor advisory
  14. 2026-07-16 14:56 UTCGHSA enrichment
  15. 2026-07-15 16:57 UTCEPSS rescore
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 14:52 UTCVendor advisory
  18. 2026-07-15 14:52 UTCGHSA enrichment
  19. 2026-07-15 02:00 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-14 14:52 UTCVendor advisory
  22. 2026-07-14 14:51 UTCGHSA enrichment
  23. 2026-07-13 22:31 UTCEPSS rescore
  24. 2026-07-13 14:52 UTCGHSA enrichment
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 36 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 14:52 UTCVendor advisory
  3. 2026-07-12 14:52 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 14:50 UTCVendor advisory
  6. 2026-07-11 14:50 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-10 14:50 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 14:50 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 14:48 UTCGHSA enrichment
  16. 2026-07-07 14:48 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 14:42 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 14:40 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-05 02:30 UTCEPSS rescore
  27. 2026-07-04 14:33 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-03 14:34 UTCGHSA enrichment
  31. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  32. 2026-07-02 14:34 UTCGHSA enrichment
  33. 2026-07-01 15:07 UTCEPSS rescore
  34. 2026-07-01 14:33 UTCGHSA enrichment
  35. 2026-06-30 14:33 UTCEG score recompute
  36. 2026-06-30 14:32 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

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 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-58013 actively exploited?
CVE-2026-58013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 25.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

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