Skip to content

← Actionable
High, CVSS 8.8amended

DDEV incomplete tar symlink traversal fix allows host file overwrite - Incomplete fix of CVE-2026-32885

CVE-2026-108262GHSA-9hq4-hm3j-jmph

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/ddev/ddev 1.25.4), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-108262: 0.31% estimated exploitation activity in the next 30 days; percentile 23.65 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The CVE-2026-32885 ZipSlip fix added a symlink-target escape check to Untar, but the check rebases an ABSOLUTE symlink target into dest before validating (filepath.Join(dest, "/etc") stays lexically inside dest and passes), while the symlink is then created with the RAW absolute target via os.Symlink(file.Linkname, ...), so a malicious archive plants a host-absolute symlink and a following regular-file entry writes through it, restoring arbitrary host file create/overwrite (reaching $HOME rc-files, hence RCE). Confirmed at HEAD.

The defect (the symlink check is a no-op for absolute targets) CVE-2026-32885 (fixed v1.25.2, commit 05cbe299) added a lexical containment check on the entry path and a NEW symlink-target validation. pkg/archive/archive.go, Untar, tar.TypeSymlink case: ```go if filepath.IsAbs(file.Linkname) { resolvedTarget = filepath.Join(dest, file.Linkname) // line 298: absolute target REBASED into dest } else { resolvedTarget = filepath.Join(fullPathDir,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-9hq4-hm3j-jmph

  2. Revision 1 · created ·

    Published from ghsa record GHSA-9hq4-hm3j-jmph

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-108262

Advisory: DDEV incomplete tar symlink traversal fix allows host file overwrite - Incomplete fix of CVE-2026-32885
IDs: CVE-2026-108262, GHSA-9hq4-hm3j-jmph
Record: https://patchnext.com/advisories/cve-2026-108262 (revision 2, source checked 10 Nov 2026, 06:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/ddev/ddev 1.25.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/ddev/ddev: affected < 1.25.4; fixed in 1.25.4

## Suggested inspection (read-only)
- Go github.com/ddev/ddev: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/ddev/ddev.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9hq4-hm3j-jmph (GitHub-reviewed advisory GHSA-9hq4-hm3j-jmph lists affected ranges: Go github.com/ddev/ddev >=0 <1.25.4)
- Verified: https://osv.dev/vulnerability/GHSA-9hq4-hm3j-jmph (OSV record GHSA-9hq4-hm3j-jmph lists affected ranges: Go github.com/ddev/ddev >=0 <1.25.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…