CVE-2026-58015: GLib: D-Bus cookie path traversal leaks local files

MEDIUM
Published June 30, 2026
CISO Take

GLib's D-Bus client accepts the cookie_context sent by a server during DBUS_COOKIE_SHA1 authentication without validating it. A malicious server can therefore use path traversal to make the client read an arbitrary local file and leak its contents by checking guesses against a hash. This is a low-urgency issue: EPSS is 0.9% (top 41%), the CVE is not in CISA KEV, CISA SSVC says TRACK, and there is no public exploit or Nuclei template. The AI relevance is indirect. GLib is a base library in Red Hat AI container images, including the RHAIIS vLLM CUDA/ROCm images, the model-opt image and the rhai base images (CPU, CUDA, ROCm, TPU, Spyre). The attack needs network position and high complexity, and it leaks only confidentiality. Apply the Red Hat errata (for example RHSA-2026:49512 and the others listed) during normal patch cycles, rebuild AI images on updated bases, and prioritize workloads that connect to untrusted D-Bus endpoints.

Sources:NVDEPSSATLASRed Hat Security Advisories (access.redhat.com)

What is the risk?

Medium-to-low risk. CVSS 5.9 reflects high attack complexity and a confidentiality-only impact. Exploitation needs the victim client to connect to an attacker-controlled D-Bus server over the network, and the attacker must guess file contents to verify them. No KEV listing, no public exploit, SSVC TRACK, and EPSS of 0.009 point to low near-term exploitation. Exposure in AI/ML environments is limited because inference containers rarely use D-Bus clients with network transports.

How does the attack unfold?

Initial Access
The attacker controls a D-Bus server or sits on the network path between a GLib client and its server.
AML.T0049
Exploitation
The server sends a cookie_context with path traversal sequences during DBUS_COOKIE_SHA1 authentication.
AML.T0037
Collection
The GLib client reads the targeted local file and computes a hash that depends on its contents.
Impact
The attacker verifies guessed contents against the hash to recover secrets such as tokens or configuration.
AML.T0025

What systems are affected?

PackageEcosystemVulnerable RangePatched
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
GLib——No patch
cert-manager/cert-manager-istio-csr-rhel9——No patch
cert-manager/cert-manager-operator-rhel9——No patch
cert-manager/cert-manager-trust-manager-rhel9——No patch
cert-manager/jetstack-cert-manager-acmesolver-rhel9——No patch
cert-manager/jetstack-cert-manager-rhel9——No patch
discovery/discovery-server-rhel9——No patch
discovery/discovery-ui-rhel9——No patch
glib2——No patch
mingw-glib2——No patch
rhai/base-image-cpu-rhel9——No patch
rhai/base-image-cuda-rhel9——No patch
rhai/base-image-rocm-rhel9——No patch
rhai/base-image-spyre-rhel9——No patch
rhai/base-image-tpu-rhel9——No patch
rhaiis/model-opt-cuda-rhel9——No patch
rhcos——No patch
rhui5/cds-kubernetes-rhel9——No patch
rhui5/cds-kubernetes-tp-rhel9——No patch
rhui5/cds-rhel9——No patch
rhui5/haproxy-rhel9——No patch
rhui5/installer-rhel9——No patch
rhui5/installer-tp-rhel9——No patch
rhui5/rhua-rhel9——No patch
rhui5/rhua-tp-rhel9——No patch

How severe is it?

CVSS 3.1
5.9 / 10
EPSS
0.8%
chance of exploitation in 30 days
Higher than 58% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Advanced

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACHigh
PRNone
UINone
SUnchanged
CHigh
INone
ANone

What should I do?

1 step
  1. 1) Apply the Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) that match your product and version. 2) Rebuild and redeploy AI/ML container images, such as vLLM and the rhai base images, on patched bases and verify the glib2 package version. 3) Do not connect to untrusted or remote D-Bus servers, and avoid TCP D-Bus transports. 4) Run containers with least-privilege file access and without secrets mounted in readable paths. 5) Detect by scanning images for the vulnerable glib2 versions and by watching for unexpected D-Bus connections to external hosts.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableNo
Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Data LeakageData ExtractionInferenceFrameworkAML.T0010.004AML.T0037

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Responses to previously unknown risks and risk treatment
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-58015?

GLib's D-Bus client accepts the cookie_context sent by a server during DBUS_COOKIE_SHA1 authentication without validating it. A malicious server can therefore use path traversal to make the client read an arbitrary local file and leak its contents by checking guesses against a hash. This is a low-urgency issue: EPSS is 0.9% (top 41%), the CVE is not in CISA KEV, CISA SSVC says TRACK, and there is no public exploit or Nuclei template. The AI relevance is indirect. GLib is a base library in Red Hat AI container images, including the RHAIIS vLLM CUDA/ROCm images, the model-opt image and the rhai base images (CPU, CUDA, ROCm, TPU, Spyre). The attack needs network position and high complexity, and it leaks only confidentiality. Apply the Red Hat errata (for example RHSA-2026:49512 and the others listed) during normal patch cycles, rebuild AI images on updated bases, and prioritize workloads that connect to untrusted D-Bus endpoints.

Is CVE-2026-58015 actively exploited?

No confirmed active exploitation of CVE-2026-58015 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-58015?

1) Apply the Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) that match your product and version. 2) Rebuild and redeploy AI/ML container images, such as vLLM and the rhai base images, on patched bases and verify the glib2 package version. 3) Do not connect to untrusted or remote D-Bus servers, and avoid TCP D-Bus transports. 4) Run containers with least-privilege file access and without secrets mounted in readable paths. 5) Detect by scanning images for the vulnerable glib2 versions and by watching for unexpected D-Bus connections to external hosts.

What systems are affected by CVE-2026-58015?

This vulnerability affects the following AI/ML architecture patterns: model serving, LLM inference containers, container base images, model optimization pipelines, Kubernetes-based ML platforms.

What is the CVSS score for CVE-2026-58015?

CVE-2026-58015 has a CVSS v3.1 base score of 5.9 (MEDIUM). The EPSS exploitation probability is 0.84%.

What is the AI security impact?

Affected AI Architectures

model servingLLM inference containerscontainer base imagesmodel optimization pipelinesKubernetes-based ML platforms

MITRE ATLAS Techniques

AML.T0010.004Container Registry
AML.T0037Data from Local System

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker gains a network position, or hosts a rogue D-Bus server, that a client process in an AI platform node connects to. During DBUS_COOKIE_SHA1 authentication the server sends a cookie_context such as ../../path/to/secret. The GLib client reads that file and returns a hash computed from it. The attacker then tests guesses against the hash to confirm or recover the file contents, such as a token or config value. Recovered credentials could later give access to model registries, inference endpoints or cloud resources.

Weaknesses (CWE)

CWE-22 — Improper Limitation of a Pathname to a Restricted Directory: The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

  • [Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylis
  • [Architecture and Design] For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

References

Timeline

Published
June 30, 2026
Last Modified
November 10, 2026
First Seen
September 30, 2026

Related Vulnerabilities