EUVD-2026-78209
GHSA-67r3-rpfh-8h3r
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network delivery via sync stream requires no workstation privileges (PR:N), but developer must actively initiate sync (UI:R); arbitrary file write yields full CIA impact on the workstation.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Path traversal during in-pod file synchronization in DevSpace through 6.3.21 allows an attacker who controls a container to write arbitrary files on the developer's workstation, enabling code execution. The sync client extracts tar entries streamed from a running pod without sanitizing parent-directory (..) sequences in entry names, so a malicious container can escape the intended sync target directory and overwrite shell RC files, SSH authorized_keys, IDE configuration, or other user-writable paths. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires the developer to be actively running 'devspace sync', 'devspace dev', or any DevSpace workflow that triggers the in-pod file sync, against a container under attacker control. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 8.7 (AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H) is broadly appropriate: the network vector and low complexity reflect that no special workstation configuration is required beyond running devspace sync, while UI:P (passive user interaction) correctly captures the developer's need to initiate the sync session. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No vendor-released patched version has been independently confirmed at the time of analysis. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all users running DevSpace version 6.3.21 or earlier and advise them to suspend pod-to-workstation file synchronization until patched; brief them that this affects only syncs involving containers outside your organization's controlled image registry. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-22 – Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today