Answer in brief
CVE-2026-17106 records a Unknown severity vulnerability in Tar extraction in moby/go-archive can write outside the destination directory via link following. The current sources do not mark it as known exploited. The current feed maps Docker/Docker CLI (generic), Docker/Docker Compose (generic), Docker/Docker Desktop (generic), Docker/Docker Engine (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-17106 records a Unknown severity vulnerability in Tar extraction in moby/go-archive can write outside the destination directory via link following. The current sources do not mark it as known exploited. The current feed maps Docker/Docker CLI (generic), Docker/Docker Compose (generic), Docker/Docker Desktop (generic), Docker/Docker Engine (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Docker/Docker CLI (generic), Docker/Docker Compose (generic), Docker/Docker Desktop (generic), Docker/Docker Engine (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Docker/Docker CLIgeneric | >=0 <29.7.0 | 29.7.0 |
| Docker/Docker Composegeneric | >=0 <5.4.0 | 5.4.0 |
| Docker/Docker Desktopgeneric | >=0 <4.86.0 | 4.86.0 |
| Docker/Docker Enginegeneric | >=0 <29.7.0 | 29.7.0 |
| Docker/Docker Sandboxesgeneric | >=0 <0.38.0 | 0.38.0 |
| moby/go-archivegeneric | >=0 <0.3.0 | 0.3.0 |
Published upstream
Aug 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 18, 2026
The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Docker/Docker CLI (generic), Docker/Docker Compose (generic), Docker/Docker Desktop (generic), Docker/Docker Engine (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Docker/Docker CLIgeneric | >=0 <29.7.0 | 29.7.0 |
| Docker/Docker Composegeneric | >=0 <5.4.0 | 5.4.0 |
| Docker/Docker Desktopgeneric | >=0 <4.86.0 | 4.86.0 |
| Docker/Docker Enginegeneric | >=0 <29.7.0 | 29.7.0 |
| Docker/Docker Sandboxesgeneric | >=0 <0.38.0 | 0.38.0 |
| moby/go-archivegeneric | >=0 <0.3.0 | 0.3.0 |
Published upstream
Aug 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 18, 2026
The tar extraction routines in moby/go-archive (Unpack, UnpackLayer, Untar/UntarUncompressed, and the ApplyLayer helpers) do not confine filesystem operations to the destination directory. The extractor decides where each archive entry lands using lexical string checks and then performs the filesystem operation on a path that is resolved by the OS, so links introduced by the archive can be followed out of the destination directory. An attacker who controls the contents of an archive can create or overwrite files at arbitrary paths writable by the extracting process.
Quoted source text, attributed separately from HOL analysis.