Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-32677

CVE-2026-32677: Gaudi Container Runtime Path Traversal

CVE-2026-32677 is a path traversal vulnerability in gaudi-container-runtime before version 1.24.0 that allows privilege escalation. This article covers the technical details, affected versions, and mitigation strategies.

Published:

CVE-2026-32677 Overview

CVE-2026-32677 is a path traversal vulnerability [CWE-22] in Intel gaudi-container-runtime versions before 1.24.0. The flaw resides within Ring 3 user applications and can allow an authenticated local user to escalate privileges on the host system. Exploitation requires local access, low attack complexity, and passive user interaction. Successful exploitation can compromise the confidentiality, integrity, and availability of the vulnerable system. Intel published Security Advisory SA-01489 to address the issue.

Critical Impact

An authenticated local attacker can traverse outside intended container runtime paths and escalate privileges, potentially gaining high-impact access to host resources managed by the Gaudi container runtime.

Affected Products

  • Intel gaudi-container-runtime versions prior to 1.24.0
  • Systems running Intel Gaudi AI accelerators with the vulnerable runtime
  • Container orchestration environments integrating the Gaudi runtime

Discovery Timeline

  • 2026-08-11 - CVE-2026-32677 published to NVD
  • 2026-08-12 - Last updated in NVD database

Technical Details for CVE-2026-32677

Vulnerability Analysis

The vulnerability is a path traversal weakness in gaudi-container-runtime, the runtime component that manages Intel Gaudi accelerator devices inside containers. Improper validation of file path inputs allows crafted paths containing traversal sequences to reference locations outside intended directories. Because the runtime executes with elevated privileges to configure device access, escaping the expected file scope translates directly into a privilege escalation opportunity on the host.

The advisory categorizes the issue as a Ring 3 user application flaw. Exploitation requires the attacker to already hold a low-privilege authenticated account on the target system. Passive user interaction is also required, meaning a legitimate user must perform an ordinary action, such as launching a container workload, for the malicious path to be processed.

Root Cause

The root cause is insufficient sanitization of user-controlled file path parameters processed by the container runtime [CWE-22]. Sequences such as ../ are not neutralized before the runtime resolves paths, permitting references to arbitrary filesystem locations outside the container context.

Attack Vector

The attack vector is local. An attacker with a valid low-privilege account supplies crafted path values that the runtime consumes when preparing a container. When a user then invokes an affected runtime operation, the traversal resolves against sensitive host paths, allowing the attacker to read, modify, or replace files accessible to the runtime process and gain elevated privileges.

No public proof-of-concept exploit is available. Technical specifics are documented in the Intel Security Advisory SA-01489.

Detection Methods for CVE-2026-32677

Indicators of Compromise

  • Container runtime log entries referencing path arguments containing ../ sequences or absolute paths outside expected mount roots.
  • Unexpected file modifications under host directories (for example /etc, /usr/local, or Gaudi device configuration paths) correlated with container startup events.
  • Processes spawned by gaudi-container-runtime accessing files unrelated to accelerator device management.

Detection Strategies

  • Audit gaudi-container-runtime invocations and inspect arguments for traversal patterns and symlink references.
  • Enable Linux audit rules (auditd) on host paths that the runtime should never touch, and alert on writes performed by runtime processes.
  • Correlate container launch events with subsequent privilege changes such as new setuid files or membership changes in privileged groups.

Monitoring Recommendations

  • Monitor package inventory to detect hosts still running gaudi-container-runtime earlier than 1.24.0.
  • Track EDR telemetry for child processes of the runtime that escape expected container namespaces.
  • Alert on file integrity changes to host binaries and configuration files during or shortly after container workloads execute.

How to Mitigate CVE-2026-32677

Immediate Actions Required

  • Upgrade gaudi-container-runtime to version 1.24.0 or later on all affected hosts.
  • Inventory systems with Intel Gaudi accelerators and confirm the runtime version deployed.
  • Restrict local shell access on Gaudi-enabled hosts to trusted operators only.

Patch Information

Intel addressed the vulnerability in gaudi-container-runtime version 1.24.0. Refer to the Intel Security Advisory SA-01489 for the authoritative fixed version list and download guidance.

Workarounds

  • Limit which accounts can submit container workloads that invoke the Gaudi runtime until patching completes.
  • Enforce mandatory access controls (SELinux or AppArmor) restricting the runtime process to required paths only.
  • Apply filesystem-level protections that block symlink and traversal resolution on directories consumed by the runtime.
bash
# Verify installed gaudi-container-runtime version and upgrade if below 1.24.0
gaudi-container-runtime --version
# Example upgrade (adjust for your package manager and distribution)
sudo apt-get update && sudo apt-get install --only-upgrade gaudi-container-runtime

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.