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.
CVE-2026-58015
Score 5.9 from GitHub Security Advisory published 2026-06-30. NVD baseline CVSS 7.5; sources differ by 1.6.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 5.9(medium)
- EPSS
- 33.7%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 2, 2026
Advisory Details (3)
Auto-updated Jun 30, 2026(#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/39312492256 – (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=2492256Vendor Advisories for CVE-2026-58015(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-58015Microsoft Security Response Center (MSRC)Medium
Glib: path traversal in glib/gio/gdbusauthmechanismsha1.c via keyring_lookup_entry and mechanism_client_data_receive
- GHSA-hmpf-72wc-2r6xGitHub Security AdvisoriesMedium
A flaw was found in GLib. The D-Bus client-side implementation of the DBUS_COOKIE_SHA1 SASL...
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.
- 2026-07-06 22:19 UTCEG score recompute
- 2026-07-06 22:19 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 21:02 UTCEG score recompute
- 2026-07-05 21:02 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 19:45 UTCEG score recompute
- 2026-07-04 19:45 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 18:28 UTCEG score recompute
- 2026-07-03 18:28 UTCGHSA enrichment
- 2026-07-02 17:11 UTCEG score recompute
- 2026-07-02 17:11 UTCGHSA enrichment
- 2026-07-01 19:07 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
- 2026-07-01 15:50 UTCEG score recompute
- 2026-07-01 15:50 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 14:33 UTCEG score recompute
- 2026-06-30 14:32 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-58015?
When was CVE-2026-58015 disclosed?
Is CVE-2026-58015 actively exploited?
What is the CVSS score of CVE-2026-58015?
How do I remediate CVE-2026-58015?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58015
Is Your Infrastructure Affected by CVE-2026-58015?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.