CVE-2026-58010

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% 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. 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
8.2(medium)
EG Risk
52(Track)
EG Risk 52/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%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
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-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(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 / 174× 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 232 total refreshes for this CVE.

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

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 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-58010 actively exploited?
CVE-2026-58010 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 67.6% of all scored CVEs.
What is the CVSS score of CVE-2026-58010?
CVE-2026-58010 has a CVSS v3 base score of 8.2 (NVD).
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

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