Is CVE-2026-50563 exploited in the wild?

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

How severe is CVE-2026-50563?

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

Which products and versions are affected?

Fission <= 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-50563?

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

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

Am I affected by CVE-2026-50563?

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-50563: Fission Container Executor privilege escalation via PodSpec injection

Q: Which products and versions are affected?

Fission <= 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-50563?

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

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

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

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

Fission is a framework for running serverless functions on Kubernetes. A vulnerability in how it handles function configurations allows a user with basic permissions to bypass security restrictions and run highly privileged code. This could allow an attacker to gain full control over the underlying server (node escape), potentially leading to the theft of sensitive data or a complete compromise of the cloud infrastructure.

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

Quick answers

Is CVE-2026-50563 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50563 being exploited in the wild.
How severe is CVE-2026-50563?: Critical severity, with a CVSS score of 9.9, published 10 June 2026.
Which products and versions are affected?: Fission <= 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-50563?: 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-50563 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-50563?: 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 vulnerability exists in Fission's Container Executor where the 'Function.spec.podspec' field is not properly validated or sanitized. Specifically, 'pkg/apis/core/v1/validation.go' fails to inspect the content of the PodSpec, and 'pkg/executor/util/merge.go' unconditionally forwards sensitive fields like 'hostPID', 'hostNetwork', and 'privileged' into the final Deployment. An attacker with 'functions.fission.io/create' permissions can submit a crafted PodSpec to mount the host root filesystem or share host namespaces. Because the executor runs with high privileges, it creates these malicious deployments on behalf of the user, leading to a container breakout and node escape. This is fixed in version 1.24.0 by implementing 'ValidatePodSpecSafety'.

Affected products

fission fission <= 1.23.0

Identifiers

CVE-2026-50563
GHSA-v455-mv2v-5g92
GO-2026-5858

Timeline

2026-05-26: disclosed
2026-06-10: advisory: NVD publication date
2026-06-30: patched: GitHub Advisory reviewed and updated

References

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