Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.7amended

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

CVE-2026-50567GHSA-q6vm-xqc9-v3ff

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/fission/fission 1.25.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N
EPSS
  • CVE-2026-50567: 0.30% estimated exploitation activity in the next 30 days; percentile 22.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-q6vm-xqc9-v3ff

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6127

  3. Revision 1 · created ·

    Published from osv record GHSA-q6vm-xqc9-v3ff

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-50567

Advisory: Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory
IDs: CVE-2026-50567, GHSA-q6vm-xqc9-v3ff
Record: https://patchnext.com/advisories/cve-2026-50567 (revision 3, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fission/fission 1.25.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fission/fission: affected <= 1.24.0; fixed in 1.25.0

## Suggested inspection (read-only)
- Go github.com/fission/fission: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fission/fission.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-q6vm-xqc9-v3ff (OSV record GHSA-q6vm-xqc9-v3ff lists affected ranges: Go github.com/fission/fission >=0 <1.25.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6127 (OSV record GO-2026-6127 lists affected ranges: Go github.com/fission/fission >=0 <1.25.0 (fixed))
- Verified: https://github.com/advisories/GHSA-q6vm-xqc9-v3ff (GitHub-reviewed advisory GHSA-q6vm-xqc9-v3ff lists affected ranges: Go github.com/fission/fission >=0 <=1.24.0)

Commands are suggestions: review each one before running it.

Loading voting…