CVE-2026-58010

HIGHNVD 8.26.5▼
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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. An off-by-one error can occur in the gvs_tuple_is_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cause a minor information disclosure of 1 byte and a denial of service when the out-of-bounds read crosses a page boundary.

CVSS v3
8.2
EG Score
6.5(medium)
EPSS
24.1%
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-190) Buffer Over-read on GLib through glib/gvariant-serialiser.c:1253 via gvs_tuple_is_normal() (#3915) · Issues · GNOME / GLib · GitLab

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

2492243 – (CVE-2026-58010) CVE-2026-58010 glib: buffer over-read in glib/gvariant-serialiser.c via gvs_tuple_is_normal()

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

cve-details

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

Vendor Advisories for CVE-2026-58010(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 24× in last 7d / 24× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 11:06 UTCEG score recompute
  4. 2026-07-06 11:06 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 11:39 UTCEG score recompute
  8. 2026-07-05 11:39 UTCGHSA enrichment
  9. 2026-07-05 02:31 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 12:15 UTCEG score recompute
  12. 2026-07-04 12:14 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-03 12:49 UTCEG score recompute
  16. 2026-07-03 12:48 UTCGHSA enrichment
  17. 2026-07-02 20:05 UTCNVD updateCVSS v3 → 8.2 · severity → HIGH
  18. 2026-07-02 13:23 UTCEG score recompute
  19. 2026-07-02 13:23 UTCGHSA enrichment
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 13:58 UTCEG score recompute
  22. 2026-07-01 13:58 UTCGHSA enrichment
  23. 2026-06-30 14:34 UTCEG score recompute
  24. 2026-06-30 14:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-58010?
CVE-2026-58010 is a high vulnerability published on June 30, 2026. A flaw was found in GLib. An off-by-one error can occur in the gvstupleis_normal function in the glib/gvariant-serialiser.c file when doing an alignment padding check because the bounds check uses > instead of >=, causing an out-of-bounds read of only 1 byte. This issue can cause a minor…
When was CVE-2026-58010 disclosed?
CVE-2026-58010 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-58010 actively exploited?
CVE-2026-58010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58010?
CVE-2026-58010 has a CVSS v3 base score of 8.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.5.
How do I remediate CVE-2026-58010?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58010, 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-58010

Explore →

Is Your Infrastructure Affected by CVE-2026-58010?

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

Start Free Scan →Browse All CVEs