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

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 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-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 58.2% 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