CVE-2026-58015

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 50% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in GLib. The D-Bus client-side implementation of the DBUS_COOKIE_SHA1 SASL authentication mechanism does not validate the cookie_context parameter received from the server. A malicious D-Bus server can supply a cookie_context containing path traversal sequences, causing the client to read an arbitrary file and exfiltrate sensitive data by verifying guessed file contents against a generated hash.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

June 30, 2026

Last Modified

September 15, 2026

Advisory Details (3)

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

(#YWH-PGM9867-203) Path Traversal on GLib DBus through glib/gio/gdbusauthmechanismsha1.c via keyring_lookup_entry, mechanism_client_data_receive (COOKIE_SHA1 Client Authentication) leads to Arbitrary File Read (sort of) (#3931) · Issues · GNOME / GLib · GitLab

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

2492256 – (CVE-2026-58015) CVE-2026-58015 glib: path traversal in glib/gio/gdbusauthmechanismsha1.c via keyring_lookup_entry and mechanism_client_data_receive

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

cve-details

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

Vendor Advisories for CVE-2026-58015(12)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-4.22.9.8.202609081748-02026-09-15redhat
redhatglib2-0:2.56.4-158.el8_6.72026-09-09redhat
redhatglib2-0:2.68.4-14.el9_4.82026-09-09redhat
redhatglib2-0:2.80.4-4.el10_0.172026-09-09redhat
redhatglib2-0:2.56.4-10.el8_4.72026-09-09redhat
redhatglib2-0:2.68.4-7.el9_2.72026-09-09redhat
redhatglib2-0:2.56.4-165.el8_8.22026-09-09redhat
redhatglib2-0:2.56.1-13.el7_9.12026-09-09redhat
redhatrhui5/rhua-rhel9:17888805812026-09-09redhat
redhatglib2-0:2.68.4-16.el9_6.72026-09-09redhat
redhatcert-manager/cert-manager-operator-rhel9:17883485222026-09-03redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17883485712026-09-03redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17883485942026-09-03redhat
redhatglib2-0:2.56.4-177.el8_102026-08-31redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
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.4-2 (146 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glib2.02.84.3-1 ... 2.89.4-2 (49 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glib2.02.84.3-1 ... 2.88.0-1 (37 versions)2.88.1-2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(9)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 22× in last 7d / 109× 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 334 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-58015?
CVE-2026-58015 is a high vulnerability published on June 30, 2026. A flaw was found in GLib. The D-Bus client-side implementation of the DBUSCOOKIESHA1 SASL authentication mechanism does not validate the cookiecontext parameter received from the server. A malicious D-Bus server can supply a cookiecontext containing path traversal sequences, causing the client to…
When was CVE-2026-58015 disclosed?
CVE-2026-58015 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58015 actively exploited?
CVE-2026-58015 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.9% of all scored CVEs.
What is the CVSS score of CVE-2026-58015?
CVE-2026-58015 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58015?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58015, 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-58015

Explore →

Is Your Infrastructure Affected by CVE-2026-58015?

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

Start Free Scan →Browse All CVEs