Is CVE-2026-50545 exploited in the wild?

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

How severe is CVE-2026-50545?

Critical severity, with a CVSS score of 9.9, published 10 June 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-50545?

Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-50545 attacked?

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

Am I affected by CVE-2026-50545?

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-50545: Fission PodSpec injection leading to node escape in Environment CRD

Q: Which products and versions are affected?

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

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

Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-50545 attacked?

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

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

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-50545 · Severity: critical · CVSS 9.9 · Published 2026-06-10

Fission, a serverless framework for Kubernetes, contains a vulnerability where users with basic permissions can bypass security checks to run highly privileged code. By injecting malicious configurations into the environment settings, an attacker can escape the isolated container and gain full control over the underlying server infrastructure. This could lead to the theft of sensitive cluster credentials and a complete takeover of the entire Kubernetes environment.

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

Quick answers

Is CVE-2026-50545 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50545 being exploited in the wild.
How severe is CVE-2026-50545?: Critical severity, with a CVSS score of 9.9, published 10 June 2026.
Which products and versions are affected?: Fission < 1.24.0, <= 1.23.0; github.com/fission/fission (Go) <= 1.23.0, SEMVER:introduced=0,fixed=1.24.0.
Is there a fix for CVE-2026-50545?: Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-50545 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50545?: 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.24.0 or later
```
go get github.com/fission/fission@v1.24.0
```

Technical details

A critical vulnerability exists in Fission due to three compounding flaws in the handling of Environment Custom Resource Definitions (CRDs). First, the validation logic in `pkg/apis/core/v1/validation.go` failed to check for dangerous PodSpec fields such as `hostPID`, `hostIPC`, `hostNetwork`, and `privileged`. Second, the admission webhook only monitored 'create' operations, allowing attackers to bypass checks by patching existing environments. Finally, the `MergePodSpec` function unconditionally propagated these dangerous fields into generated deployments. An attacker with basic RBAC permissions to create or update environments can schedule a privileged pod with host-root mounts, enabling them to read the cluster CA private key and achieve full cluster takeover. The issue is fixed in version 1.24.0.

Affected products

fission fission <= 1.23.0

Identifiers

CVE-2026-50545
GHSA-wmgg-3p4h-48x7
GO-2026-5860

Timeline

2026-05-26: disclosed
2026-06-10: advisory: NVD publication date
2026-06-30: patched: GitHub Advisory published/updated with fix details

References

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