DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names from the in-pod sync stream. (CVE-2026-91200)
DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names from the in-pod sync stream. Attackers operating a malicious container can stream tar entries with traversal sequences to write arbitrary files on the developer workstation, enabling code execution.
AI Analysis
Technical Summary
The vulnerability in DevSpace up to version 6.3.21 involves improper validation of tar entry names received from the in-pod sync stream. Specifically, the software fails to reject parent-directory traversal sequences (e.g., '..') in tar entry paths. An attacker controlling a malicious container can exploit this to write files outside the intended directory on the developer's workstation, potentially leading to arbitrary code execution.
Potential Impact
Successful exploitation allows an attacker with control over a container to write arbitrary files on the developer's workstation, which can lead to code execution with the privileges of the developer. This compromises confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running untrusted containers or restrict the use of the in-pod sync feature with untrusted sources.
DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names from the in-pod sync stream. (CVE-2026-91200)
Description
DevSpace through 6.3.21 fails to reject parent-directory segments in tar entry names from the in-pod sync stream. Attackers operating a malicious container can stream tar entries with traversal sequences to write arbitrary files on the developer workstation, enabling code execution.
CVSS v3.1
Score 8.8high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in DevSpace up to version 6.3.21 involves improper validation of tar entry names received from the in-pod sync stream. Specifically, the software fails to reject parent-directory traversal sequences (e.g., '..') in tar entry paths. An attacker controlling a malicious container can exploit this to write files outside the intended directory on the developer's workstation, potentially leading to arbitrary code execution.
Potential Impact
Successful exploitation allows an attacker with control over a container to write arbitrary files on the developer's workstation, which can lead to code execution with the privileges of the developer. This compromises confidentiality, integrity, and availability of the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid running untrusted containers or restrict the use of the in-pod sync feature with untrusted sources.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-67r3-rpfh-8h3r
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-91200"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aa8a15c55bf5e2cf5f3b6de
Added to database: 09/15/2026, 01:37:32 UTC
Last enriched: 09/15/2026, 01:40:12 UTC
Last updated: 09/15/2026, 03:18:18 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.