DDEV incomplete tar symlink traversal fix allows host file overwrite - Incomplete fix of CVE-2026-32885
- Exploited
- No known exploitation
- Fix
- Fixed in 1.25.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.25.4.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
DDEV, an open-source tool for local PHP and Node.js web development, has a flaw in its tar extraction code that lets a crafted archive write files outside the extraction directory on the host. An attacker can reach it remotely without logging in, but the victim must take an action such as importing a crafted archive, and the incomplete fix means this issue still affects some versions.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
DDEV is an open-source tool for running local web development environments for PHP and Node.js. From 1.25.2 until 1.25.4, Untar in pkg/archive/archive.go validates an absolute tar symlink target after rebasing it beneath dest, but creates the symlink with the raw absolute Linkname. A crafted archive can therefore plant a host-absolute symlink and use a following regular-file entry to write outside the extraction directory. The flaw is reachable through remote add-on retrieval and database or file imports, and overwriting shell startup files, Git hooks, or cron entries can lead to code execution in the DDEV user's context. Unzip is not affected. This issue is fixed in version 1.25.4.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.25.4.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- ddev ddev
From 1.25.2 · fixed in 1.25.4
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-108262
Is CVE-2026-108262 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-108262?
ddev: from 1.25.2 before 1.25.4.Source: cve.now feed data
How do I fix CVE-2026-108262?
Upgrade to a fixed version: 1.25.4.Source: cve.now feed data