Is CVE-2026-50568 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50568 being exploited in the wild.

How severe is CVE-2026-50568?

Low severity, with a CVSS score of 3.6, published 10 June 2026.

Which products and versions are affected?

Fission < 1.25.0, <= 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-50568?

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-50568 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-50568?

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.

CVE-2026-50568: Fission path traversal in SanitizeFilePath utility

Q: Which products and versions are affected?

Fission < 1.25.0, <= 1.24.0; github.com/fission/fission (Go) <= 1.24.0, SEMVER:introduced=0,fixed=1.25.0.

Q: Is there a fix for CVE-2026-50568?

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.

Q: How is CVE-2026-50568 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-50568?

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.

CVE-2026-50568 · Severity: low · CVSS 3.6 · Published 2026-06-10

Fission is a framework for serverless functions on Kubernetes. A flaw in how it validates file paths allows a user to potentially read or write files in folders they should not have access to, provided they can control a folder with a similar name on the same system. This could lead to unauthorized data access or modification within the shared storage used by the Fission builder and fetcher components.

Technologies: Fission, github.com/fission/fission (Go). Vendors: Fission, Go.

Quick answers

Is CVE-2026-50568 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50568 being exploited in the wild.
How severe is CVE-2026-50568?: Low severity, with a CVSS score of 3.6, published 10 June 2026.
Which products and versions are affected?: Fission < 1.25.0, <= 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-50568?: 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-50568 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-50568?: 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

The `SanitizeFilePath` function in `pkg/utils/utils.go` used a lexical prefix check (`strings.HasPrefix`) to validate that a path remained within a designated safe directory. Because it did not enforce a path-separator boundary, a path like `/packages-extra/` would be incorrectly validated against a safe directory of `/packages`. An attacker with the ability to control or pre-create sibling directories on the shared volume used by the builder or fetcher can exploit this to achieve arbitrary file reads or writes outside the intended scope. The vulnerability was addressed in version 1.25.0 by migrating to `os.Root` for directory confinement and removing the flawed `SanitizeFilePath` function.

Affected products

fission fission <= 1.24.0

Identifiers

CVE-2026-50568
GHSA-r5jh-q2mw-gcx4
GO-2026-6130

Timeline

2026-06-08: disclosed
2026-06-10: advisory: NVD publication
2026-07-28: patched: GitHub Advisory published/updated with fix version 1.25.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.