CVE-2026-17106: Tar extraction in moby/go-archive can write outside the destination directory via link following
Noroxi assessment
Priority: Monitor (action score 28/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.44% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: Docker Docker CLI 29.7.0; Docker Docker Compose 5.4.0; Docker Docker Desktop 4.86.0.
Low priority for now. Upgrade to Docker Docker CLI 29.7.0; Docker Docker Compose 5.4.0; Docker Docker Desktop 4.86.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-16238
- GHSA-hfg8-hc9c-6c3h
- ALSA-2026:69961
- ALSA-2026:70201
- GO-2026-6253
- openSUSE-SU-2026:11544-1
- openSUSE-SU-2026:12068-1
- openSUSE-SU-2026:12260-1
- openSUSE-SU-2026:12341-1
- openSUSE-SU-2026:21611-1
- openSUSE-SU-2026:21761-1
- RHSA-2026:52807
- RHSA-2026:69961
- RHSA-2026:70201
- RLSA-2026:69961
- RLSA-2026:70201
- SUSE-SU-2026:23625-1
- SUSE-SU-2026:3863-1
- Published
- Aug 18, 2026
- Updated
- Aug 28, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-59
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Docker
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Docker). Independent of NVD's CPE analysis and usually ahead of it.
Docker Docker CLI
- before 29.7.0affected · semver
Docker Docker Compose
- before 5.4.0affected · semver
Docker Docker Desktop
- before 4.86.0affected · semver
Docker Docker Engine
- before 29.7.0affected · semver
Docker Docker Sandboxes
- before 0.38.0affected · semver
moby go-archive
- before 0.3.0affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | podman | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-docker | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-remote | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:10 | podman-tests | before 7:5.8.2-9.el10_2.alma.1 | 7:5.8.2-9.el10_2.alma.1 |
| AlmaLinux:9 | podman | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-docker | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-plugins | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-remote | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| AlmaLinux:9 | podman-tests | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
| Debian:14 | golang-github-moby-go-archive | before 0.3.3-1 | 0.3.3-1 |
| Go | github.com/moby/go-archive | before 0.3.0 | 0.3.0 |
| openSUSE:Leap 16.0 | apptainer | before 1.5.3-bp160.2.1 | 1.5.3-bp160.2.1 |
| openSUSE:Leap 16.0 | govulncheck-vulndb | before 0.0.20260827T195228-160000.1.1 | 0.0.20260827T195228-160000.1.1 |
| openSUSE:Tumbleweed | apptainer | before 1.5.3-2.1 | 1.5.3-2.1 |
| openSUSE:Tumbleweed | buildah | before 1.46.0-1.1 | 1.46.0-1.1 |
| openSUSE:Tumbleweed | buildpacks-cli | before 0.40.10-1.1 | 0.40.10-1.1 |
| openSUSE:Tumbleweed | podman | before 6.1.2-1.1 | 6.1.2-1.1 |
| Red Hat:hummingbird:1 | podman | before 5:6.0.2-2.2.hum1 | 5:6.0.2-2.2.hum1 |
| Red Hat:hummingbird:1 | podman-docker | before 5:6.0.2-2.2.hum1 | 5:6.0.2-2.2.hum1 |
| Red Hat:hummingbird:1 | podman-machine | before 5:6.0.2-2.2.hum1 | 5:6.0.2-2.2.hum1 |
| Red Hat:hummingbird:1 | podman-remote | before 5:6.0.2-2.2.hum1 | 5:6.0.2-2.2.hum1 |
| Red Hat:hummingbird:1 | podmansh | before 5:6.0.2-2.2.hum1 | 5:6.0.2-2.2.hum1 |
| Rocky Linux:10 | podman | before 7:5.8.2-9.el10_2 | 7:5.8.2-9.el10_2 |
| Rocky Linux:9 | podman | before 6:5.8.2-7.el9_8 | 6:5.8.2-7.el9_8 |
+2
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Docker Docker CLI | 29.7.0 | Vendor (CNA) |
| Docker Docker Compose | 5.4.0 | Vendor (CNA) |
| Docker Docker Desktop | 4.86.0 | Vendor (CNA) |
| Docker Docker Engine | 29.7.0 | Vendor (CNA) |
| Docker Docker Sandboxes | 0.38.0 | Vendor (CNA) |
| moby go-archive | 0.3.0 | Vendor (CNA) |
| azl3 docker-cli 25.0.7-4 on Azure Linux 3.0 | 25.0.7-5 | Microsoft (MSRC) |
| azl3 docker-cli 25.0.7-5 on Azure Linux 3.0 | 25.0.7-5 | Microsoft (MSRC) |
| azl3 moby-engine 25.0.3-19 on Azure Linux 3.0 | 25.0.3-20 | Microsoft (MSRC) |
| azl3 moby-engine 25.0.3-20 on Azure Linux 3.0 | 25.0.3-20 | Microsoft (MSRC) |
| almalinux:podman | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-docker | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-plugins | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-remote | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:podman-tests | 6:5.8.2-7.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| debian:golang-github-moby-go-archive | 0.3.3-1 · Debian:14 | Package registry (OSV) |
| Go:github.com/moby/go-archive | 0.3.0 | Package registry (OSV) |
| opensuse:apptainer | 1.5.3-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:buildah | 1.46.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:buildpacks-cli | 0.40.10-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20260827T195228-160000.1.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| opensuse:podman | 6.1.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:podman | 0:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman | 5:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-debuginfo | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-debugsource | 6:5.8.2-7.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:podman-docker | 0:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-docker | 5:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-machine | 0:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:podman-machine | 5:6.0.2-2.2.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
+13
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×4
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 4 repositories | 2026-08-09 → 2026-10-23 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-10 d
- Published
- TodayNov 16, 2026+90 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.