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

> Attackers can write arbitrary files outside the destination directory via malicious zip archives, potentially compromising other tenants or executing code.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-q6vm-xqc9-v3ff, GO-2026-6127

## What is CVE-2026-50567?

CVE-2026-50567 is a high-severity path traversal vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.25.0, 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. This issue has been patched in version 1.25.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-50567?

3 open source packages ship an affected version, including github.com/fission/fission.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |

## How do I fix CVE-2026-50567?

Upgrade github.com/fission/fission to 1.25.0 or later.

## Is CVE-2026-50567 being exploited?

There is no known exploitation of CVE-2026-50567 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50567 and fix it if it is affected.

What it is: CVE-2026-50567 is a high-severity path traversal vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50567 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50567/ (Markdown: https://insights.sbomify.com/CVE-2026-50567/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50567
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50567
- OSV: https://osv.dev/vulnerability/CVE-2026-50567

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50567/
Summaries are generated and may contain mistakes; the official description above is the record.