Openbao: tar extraction routines
Affects openbaoSource GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 2.5.5-r2 soon.
Data as of 20 Nov 2026, 03:34 UTC
- Patch
- Available – fixed in 2.5.5-r2
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by Docker Inc.
, 25 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, the same day as disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade openbao to 2.5.5-r2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
CleanStartopenbaopkg:apk/cleanstart/openbaoOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade openbao to version 2.5.5-r2 or later, where the vulnerability in the tar extraction routines has been fixed. Applying this official fix will prevent filesystem operations from escaping the destination directory during extraction.
Description
A security vulnerability in the openbao package affects the tar extraction routines in moby/go-archive, specifically the Unpack, UnpackLayer, Untar/UntarUncompressed, and ApplyLayer helpers. These routines do not properly confine filesystem operations to the intended destination directory, potentially allowing unauthorized file system modifications. The issue affects versions prior to 2.5.5-r2 and has been assigned CVE-2026-17106 with a high severity rating. A fix is available in version 2.5.5-r2.