CVE-2026-32885
Path Traversal in DDEV Archive Extraction Allows Arbitrary File Write
Publication date: 2026-04-22
Last updated on: 2026-04-22
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ddev | ddev | to 1.25.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in DDEV, an open-source tool used for running local web development environments for PHP and Node.js. Versions before 1.25.2 have a flaw in the `Untar()` and `Unzip()` functions located in `pkg/archive/archive.go`. These functions perform extraction of archives downloaded from remote sources without validating the paths inside the archives. This lack of path validation can lead to unsafe extraction behavior.
How can this vulnerability impact me? :
Because the extraction functions do not validate paths, an attacker could craft a malicious archive that, when extracted, overwrites or modifies files outside the intended directory. This can lead to integrity issues, such as unauthorized modification of files, potentially allowing code injection or other harmful impacts. The CVSS score indicates a medium severity with high impact on integrity.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade DDEV to version 1.25.2 or later, as this version patches the unsanitized extraction issue in the Untar() and Unzip() functions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows arbitrary file writes outside the intended extraction directory due to path traversal in archive extraction functions. This can lead to unauthorized modification of files on a developer's machine.
While the CVE description and resources do not explicitly mention compliance with standards like GDPR or HIPAA, the ability to write arbitrary files could potentially impact data integrity and security controls required by such regulations.
Specifically, the integrity impact is rated high, which may violate requirements for protecting data integrity under these regulations. However, there is no direct confidentiality or availability impact noted.
Therefore, organizations using vulnerable versions of DDEV might face increased risk of non-compliance if this vulnerability is exploited to alter critical files or configurations related to regulated data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if your system is running a version of DDEV prior to 1.25.2, as these versions contain the vulnerable Untar() and Unzip() functions that do not sanitize extraction paths.
To detect exploitation attempts or presence of malicious files, you can look for unexpected files created outside of intended extraction directories, especially files with path traversal patterns in their names.
Since the vulnerability involves extraction of archives with crafted filenames containing directory traversal sequences, monitoring file creation events outside expected directories during archive extraction can help detect exploitation.
Specific commands to detect the vulnerability or exploitation attempts are not provided in the available resources.