HighGHSA-q6vm-xqc9-v3ffCVE-2026-50567GO-2026-6127

Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory

Published 28 Jul 2026 · Updated 18 Aug 2026

Is your project on an affected github.com/fission/fission?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.25.0
Fixed in
1.25.0
Update to the fixed version for your release line, for example:go get github.com/fission/fission@v1.25.0

Details

Unarchive in pkg/utils/zip.go joined each archive entry name with the destination directory via filepath.Join and wrote the result without checking whether the resolved path stayed under the destination. A zip entry named ../../tmp/evil therefore landed at /tmp/evil. An attacker who could control a Package.Spec.Source.URL or Deployment.URL archive could induce the fetcher (running as the per-environment pod's fission-fetcher sidecar) to write files anywhere that process could reach: into other tenants' /packages/<ns>/ directories, into mounted secret/config volumes, or into the fetcher's own binary.

### Affected

  • Project: github.com/fission/fission
  • Versions: all up to and including v1.24.0
  • Audited commit: 647c141
  • Component: pkg/utils/zip.go (Unarchive)
  • Configuration: default; triggered when the fetcher downloads and extracts a zip archive

Fix section (paste into the Fix / Patches field)

Fixed in v1.25.0 by:

  • PR #3444 (commit `55704aca`) — Unarchive now opens an os.Root on the destination, validates each archive entry name (rejects absolute paths and .. traversal), and refuses symlink entries up front. The os.Root confines every mkdir / create to the destination in the kernel.

Regression coverage: TestUnarchiveZipSlip in pkg/utils/zip_test.go exercises parent-traversal, absolute-path, and symlink entries.

Is GHSA-q6vm-xqc9-v3ff in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fission/fission, and gives you the command that fixes it.

More advisories for github.com/fission/fission

  • LowCVE-2026-50570Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption in github.com/fission/fission · 18 Aug 2026
  • LowCVE-2026-50568Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape in github.com/fission/fission · 18 Aug 2026
  • LowCVE-2026-50569Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks in github.com/fission/fission · 18 Aug 2026
  • LowCVE-2026-50568Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape · 28 Jul 2026
  • MediumCVE-2026-50569Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks · 28 Jul 2026
  • HighCVE-2026-50570Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption · 28 Jul 2026
All 35 advisories for github.com/fission/fission

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.