Is CVE-2026-50569 exploited in the wild?

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

How severe is CVE-2026-50569?

Medium severity, with a CVSS score of 4.3, 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-50569?

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

It is attacked over the network, in a software library.

Am I affected by CVE-2026-50569?

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-50569: Fission HTTPTrigger improper input validation in RelativeURL and Prefix

Q: 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.

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

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

It is attacked over the network, in a software library.

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

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-50569 · Severity: medium · CVSS 4.3 · Published 2026-06-10

Fission, a serverless framework for Kubernetes, contained a vulnerability where certain web request triggers were not properly validated when created through standard Kubernetes tools. This allowed users with basic permissions to create malicious triggers that could intercept traffic intended for the system's core management functions or other internal services. An attacker could use this to disrupt operations or redirect traffic to unauthorized functions.

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

Quick answers

Is CVE-2026-50569 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50569 being exploited in the wild.
How severe is CVE-2026-50569?: Medium severity, with a CVSS score of 4.3, 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-50569?: 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-50569 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50569?: 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 HTTPTriggerSpec.Validate() function and the API-server Common Expression Language (CEL) rules failed to validate the 'RelativeURL' and 'Prefix' fields, relying solely on client-side CLI checks. An attacker with permissions to create HTTPTriggers could bypass these CLI checks using 'kubectl apply' or direct REST API calls to inject malicious paths. This includes creating triggers with empty paths, path traversal segments (..), or paths that collide with reserved router routes (e.g., /router-healthz, /auth/login) and internal function prefixes. The vulnerability is fixed in version 1.25.0 by implementing server-side validation in both Go and CEL.

Affected products

fission fission <= 1.24.0

Identifiers

CVE-2026-50569
GHSA-vchh-r53j-8mpw
GO-2026-6131

Timeline

2026-06-08: disclosed
2026-06-10: advisory: NVD publication
2026-07-28: patched: GitHub Advisory updated with patch details

References

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