CVE-2026-91200: DevSpace Path Traversal Vulnerability

CVE-2026-91200 Overview

CVE-2026-91200 is a path traversal vulnerability [CWE-22] in DevSpace versions through 6.3.21. DevSpace is a developer tool for building, deploying, and debugging applications in Kubernetes clusters. The tool synchronizes files between developer workstations and in-pod containers using a tar-based stream. DevSpace fails to reject parent-directory segments (../) in tar entry names received from the in-pod sync stream. An attacker running a malicious container can craft tar entries with traversal sequences to write files outside the intended sync directory on the developer workstation, resulting in arbitrary file write and code execution.

Critical Impact
A malicious container can write arbitrary files to a developer workstation over the DevSpace sync channel, leading to code execution in the developer's user context.

Affected Products

DevSpace versions through 6.3.21
Developer workstations running DevSpace file sync sessions
Kubernetes environments where developers sync against untrusted or attacker-controlled pods

Discovery Timeline

2026-09-14 - CVE-2026-91200 published to NVD
2026-09-15 - Last updated in NVD database

Technical Details for CVE-2026-91200

Vulnerability Analysis

DevSpace's in-pod sync feature streams files between a container and the developer workstation using tar archives. When the workstation receives an archive from the pod, it iterates over each tar entry and writes files to a destination directory. The extraction logic in pkg/devspace/sync/tar.go does not validate that the resolved entry path stays within the intended sync root. Because tar headers can carry names such as ../../etc/host_file or absolute paths, an attacker controlling the pod can direct writes to arbitrary locations reachable by the DevSpace process. The impact scales with the privileges of the developer running devspace sync or devspace dev, which typically include write access to shell startup files, SSH configuration, and user-invoked binaries.

Root Cause

The extraction routine trusts tar entry names supplied by the remote peer. Reference implementations at DevSpace tar sync code and DevSpace sync utility code show that path joining is performed without normalizing or rejecting .. segments. The design assumes the container is a trusted peer, which does not hold when developers attach DevSpace to third-party or compromised images. See DevSpace issue #3290 and the VulnCheck advisory for additional context.

Attack Vector

Exploitation requires the developer to initiate a sync session against a malicious pod. The attacker's container runs the DevSpace pod-side helper and streams a tar archive containing entries whose names include parent-directory traversal or absolute paths. When the workstation extracts the stream, it writes attacker-chosen content to attacker-chosen paths within the user's writable filesystem. Common post-exploitation targets include shell profile files (~/.bashrc, ~/.zshrc), SSH configuration (~/.ssh/authorized_keys, ~/.ssh/config), and Git hooks in local repositories. Code execution follows on the next shell invocation or interactive session.

No verified public proof-of-concept code is available. Refer to the VulnCheck advisory for technical detail.

Detection Methods for CVE-2026-91200

Indicators of Compromise

Unexpected file writes outside the configured DevSpace sync directory on developer workstations during or shortly after a devspace dev or devspace sync session.
Modifications to shell startup files (~/.bashrc, ~/.zshrc, ~/.profile) or SSH configuration files timestamped to a DevSpace sync window.
DevSpace processes spawning writes to paths that resolve through .. segments relative to the declared sync root.

Detection Strategies

Monitor process telemetry for the DevSpace CLI opening file descriptors outside the project directory tree.
Alert on tar entries in captured sync streams whose names contain .. or begin with / when static analysis or logging proxies are available.
Correlate Kubernetes pull events for untrusted images with subsequent workstation file modifications in sensitive directories.

Monitoring Recommendations

Enable filesystem auditing on developer endpoints for writes to ~/.ssh/, shell rc files, and ~/.local/bin/.
Ingest DevSpace CLI logs and Kubernetes audit logs into a central data lake to correlate sync sessions with anomalous file activity.
Track use of container images from untrusted registries in developer environments and flag DevSpace attachments to those workloads.

How to Mitigate CVE-2026-91200

Immediate Actions Required

Restrict DevSpace usage to trusted, first-party container images and internal registries until a patched release is available.
Avoid running devspace dev or devspace sync against pods derived from unverified public images or shared multi-tenant clusters.
Run DevSpace under a least-privileged OS user account that lacks write access to SSH keys and shell configuration.

Patch Information

No fixed version is identified in the enriched CVE data. Track the DevSpace GitHub repository and DevSpace issue #3290 for a security release addressing tar entry name validation. Upgrade to a patched release beyond 6.3.21 once published, and validate the release notes reference CVE-2026-91200.

Workarounds

Execute DevSpace inside an ephemeral sandbox such as a disposable VM or container so tar traversal writes cannot reach persistent developer state.
Configure Kubernetes admission policies to prevent developers from attaching sync sessions to pods running images outside an approved allowlist.
Review DevSpace configuration to disable in-pod sync features where they are not required for the workflow.

bash

# Configuration example: run devspace inside a rootless container sandbox
# so any traversal writes are confined to a disposable filesystem.
docker run --rm -it \
  --user 1000:1000 \
  -v "$PWD":/workspace:rw \
  -v "$HOME/.kube":/home/dev/.kube:ro \
  -w /workspace \
  devspace-sandbox:latest \
  devspace dev