Quick answers
- Is CVE-2026-50567 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50567 being exploited in the wild.
- How severe is CVE-2026-50567?
- High severity, with a CVSS score of 7.7, published 10 June 2026.
- Which products and versions are affected?
- Fission <= 1.24.0; github.com/fission/fission (Go) <= 1.24.0, SEMVER:introduced=0,fixed=1.25.0.
- Is there a fix for CVE-2026-50567?
- Yes. github.com/fission/fission (Go): upgrade to 1.25.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50567 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50567?
- Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/fission/fission (Go): upgrade to 1.25.0 or later
go get github.com/fission/fission@v1.25.0
Technical details
A path traversal vulnerability, commonly known as 'Zip Slip', exists in the `Unarchive` function within `pkg/utils/zip.go`. The component uses `filepath.Join` to combine archive entry names with the destination directory without verifying if the resulting path remains within the target boundaries. An attacker who can control a `Package.Spec.Source.URL` or `Deployment.URL` can provide a ZIP archive containing entries with `../` sequences. This allows the `fission-fetcher` sidecar to write files to arbitrary locations accessible to the process, including mounted secret volumes or other tenant directories. The issue is fixed in version 1.25.0 by implementing `os.Root` for directory confinement and validating entry names against traversal sequences and symlinks.
Affected products
- fission fission <= 1.24.0
Identifiers
- CVE-2026-50567
- GHSA-q6vm-xqc9-v3ff
- GO-2026-6127
Timeline
- 2026-06-08: disclosed
- 2026-06-10: advisory: NVD publication
- 2026-07-28: patched: GitHub Advisory updated/published