CVE-2026-108262 · Package
NO FIX YET · SEE WHAT TO DO
DDEV, a local web development tool, extracts tar archives in a way that lets a crafted archive plant an absolute symlink and then write files outside the extraction folder. An attacker who gets a developer to fetch an add-on or import a database or file can overwrite shell startup files, Git hooks or cron entries, leading to code execution as the DDEV user.
first public Sep 2, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Developers running DDEV from 1.25.2 up to but not including 1.25.4 are exposed, especially when they fetch remote add-ons or import database or file archives from untrusted sources. Unzip handling is not affected. Teams on older or newer releases, or who only use local trusted content, can skip it.
Not affected if trusted-imports-only, unzip-only
Who cares ddev, local-dev, node.js, php
Unknown from the sources.
1.25.4.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.