Path Traversal in github.com/portainer/portainer (CVE-2026-44885)
Summary
Path traversal in github.com/portainer/portainer (CVE-2026-44885). Data can be tampered with by attackers. Exploitable via ExtractTarGz. Mitigation: upgrade to 2.33.8 or later.
Original description
The description as published by the source.
Portainer Community Edition is a lightweight service delivery platform for containerized applications that can be used to manage Docker, Swarm, Kubernetes and ACI environments. From 2.33.0 to before 2.33.8, Portainer's backup restore feature accepts a .tar.gz archive and extracts it to a target directory on the server. The extraction function (ExtractTarGz in api/archive/targz.go) constructed output paths using filepath.Clean(filepath.Join(outputDirPath, header.Name)). This combination does not prevent directory traversal — a tar entry named ../../etc/cron.d/evil resolves to a path outside the extraction root, so a crafted archive can write files to arbitrary locations on the server filesystem. This vulnerability is fixed in 2.33.8.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44885 has been found in github.com/portainer/portainer.
Attackers can target a specific entry point like ExtractTarGz over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.5/10.
What to do: upgrade github.com/portainer/portainer to 2.33.8 or later.
If unsure, ask your IT team or search "github.com/portainer/portainer CVE-2026-44885" on the vendor's site.
CVE-2026-44885 (github.com/portainer/portainer) — CWE-22 / CVSS v3 5.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ExtractTarGz / develop
Patched: 2.33.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/portainer/portainer. Attackers reach the vulnerable code path via ExtractTarGz.
Check the vendor advisory for the affected versions of github.com/portainer/portainer. Attack surface: ExtractTarGz / develop.
Severity: Medium (CVSS 5.5/10). Data can be tampered with by attackers.
Update to 2.33.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/portainer/portainer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/portainer/portainer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/portainer/portainerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/portainer/portainer to 2.33.8ステージング環境で 2.33.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com