CVE-2026-58016

CRITICALNVD 9.17.5▼
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-30. NVD baseline CVSS 9.1; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: 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 state confusion issue exists in g_dbus_node_info_new_for_xml() in the gio/gdbusintrospection.c file when processing malformed D-Bus introspection XML, specifically with a element nested within other elements like , , or . This issue can cause an unsigned integer overflow and lead to an out-of-bounds read, resulting in a denial of service.

CVSS v3
9.1
EG Score
7.5(medium)
EPSS
34.4%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 21, 2026

Advisory Details (3)

Auto-updated Jun 30, 2026
🔬 Proof of concept available. Patch available. Sources: redhat.
generic🟡 PoC Available

(#YWH-PGM9867-204) Integer Underflow (CWE-191) on GLib through gio/gdbusintrospection.c via "g_dbus_node_info_new_for_xml" (#3932) · Issues · GNOME / GLib · GitLab

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

2492257 – (CVE-2026-58016) CVE-2026-58016 glib: integer underflow in gio/gdbusintrospection.c via "g_dbus_node_info_new_for_xml"

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

cve-details

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

Vendor Advisories for CVE-2026-58016(5)

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 15× in last 7d / 83× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 03:06 UTCVendor advisory
  10. 2026-07-17 03:06 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 15:47 UTCVendor advisory
  13. 2026-07-16 15:47 UTCGHSA enrichment
  14. 2026-07-16 04:13 UTCVendor advisory
  15. 2026-07-16 04:13 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:55 UTCVendor advisory
  19. 2026-07-15 16:55 UTCGHSA enrichment
  20. 2026-07-15 05:36 UTCVendor advisory
  21. 2026-07-15 05:36 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 18:03 UTCVendor advisory
  25. 2026-07-14 18:03 UTCGHSA enrichment
Show 58 more
  1. 2026-07-14 06:26 UTCVendor advisory
  2. 2026-07-14 06:25 UTCGHSA enrichment
  3. 2026-07-13 22:31 UTCEPSS rescore
  4. 2026-07-13 19:06 UTCGHSA enrichment
  5. 2026-07-13 07:48 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 20:30 UTCVendor advisory
  9. 2026-07-12 20:30 UTCGHSA enrichment
  10. 2026-07-12 09:13 UTCVendor advisory
  11. 2026-07-12 09:13 UTCGHSA enrichment
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 21:56 UTCVendor advisory
  14. 2026-07-11 21:56 UTCGHSA enrichment
  15. 2026-07-11 10:39 UTCVendor advisory
  16. 2026-07-11 10:39 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-10 23:21 UTCGHSA enrichment
  20. 2026-07-10 12:03 UTCGHSA enrichment
  21. 2026-07-10 00:44 UTCGHSA enrichment
  22. 2026-07-09 19:10 UTCEPSS rescore
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 13:22 UTCGHSA enrichment
  25. 2026-07-09 02:04 UTCGHSA enrichment
  26. 2026-07-08 15:16 UTCEPSS rescore
  27. 2026-07-08 15:16 UTCEPSS rescore
  28. 2026-07-08 14:44 UTCGHSA enrichment
  29. 2026-07-08 03:25 UTCGHSA enrichment
  30. 2026-07-07 16:08 UTCGHSA enrichment
  31. 2026-07-07 13:46 UTCEPSS rescore
  32. 2026-07-07 13:46 UTCEPSS rescore
  33. 2026-07-07 04:50 UTCGHSA enrichment
  34. 2026-07-06 17:32 UTCGHSA enrichment
  35. 2026-07-06 16:27 UTCEPSS rescore
  36. 2026-07-06 16:27 UTCEPSS rescore
  37. 2026-07-06 06:11 UTCGHSA enrichment
  38. 2026-07-06 02:23 UTCEPSS rescore
  39. 2026-07-06 02:23 UTCEPSS rescore
  40. 2026-07-05 18:52 UTCGHSA enrichment
  41. 2026-07-05 07:34 UTCGHSA enrichment
  42. 2026-07-05 02:31 UTCEPSS rescore
  43. 2026-07-05 02:30 UTCEPSS rescore
  44. 2026-07-04 20:17 UTCGHSA enrichment
  45. 2026-07-04 08:59 UTCGHSA enrichment
  46. 2026-07-04 06:31 UTCEPSS rescore
  47. 2026-07-04 06:31 UTCEPSS rescore
  48. 2026-07-03 21:42 UTCGHSA enrichment
  49. 2026-07-03 10:25 UTCGHSA enrichment
  50. 2026-07-02 23:04 UTCGHSA enrichment
  51. 2026-07-02 11:46 UTCGHSA enrichment
  52. 2026-07-02 00:28 UTCGHSA enrichment
  53. 2026-07-01 19:07 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  54. 2026-07-01 15:07 UTCEPSS rescore
  55. 2026-07-01 13:08 UTCGHSA enrichment
  56. 2026-07-01 01:51 UTCGHSA enrichment
  57. 2026-06-30 14:33 UTCEG score recompute
  58. 2026-06-30 14:32 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-58016?
CVE-2026-58016 is a critical vulnerability published on June 30, 2026. A flaw was found in GLib. A state confusion issue exists in gdbusnodeinfonewforxml() in the gio/gdbusintrospection.c file when processing malformed D-Bus introspection XML, specifically with a <node> element nested within other elements like <method>, <signal>, <property> or <arg>. This issue can…
When was CVE-2026-58016 disclosed?
CVE-2026-58016 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58016 actively exploited?
CVE-2026-58016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58016?
CVE-2026-58016 has a CVSS v3 base score of 9.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.5.
How do I remediate CVE-2026-58016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58016, 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-58016

Explore →

Is Your Infrastructure Affected by CVE-2026-58016?

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

Start Free Scan →Browse All CVEs