CVE-2026-50564: github.com/fission/fission · Fission Environment CRD podspec passthrough enables hostPID/hostNetwork/privileged pods, node escape
Affects github.com/fission/fissionSource GCVE Database
Not known to be exploited · CVSS 9.9 Critical : upgrade to 1.24.0 as a priority.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.24.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 30 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade github.com/fission/fission to 1.24.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/fission/fission | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Fission version 1.24.0. This update implements an admission denylist that rejects Environment CRD pod specs containing hostNetwork, hostPID, hostIPC, privileged containers, and other dangerous settings. It also sanitizes these fields during pod spec merging to prevent bypass. Users should upgrade to v1.24.0 or later to mitigate this vulnerability. Prior to upgrading, restricting create/update RBAC permissions on environments.fission.io can reduce risk.
Description
Fission's Environment Custom Resource Definition (CRD) allowed users with create/update permissions to specify pod specifications that could enable privileged pods with host network, host PID, and other sensitive capabilities. This flaw enabled potential node escape and full node compromise. The vulnerability was fixed in Fission version 1.24.0 by adding admission denylist checks and sanitizing pod specs during merge. Prior to this fix, Kubernetes Pod Security Admission did not prevent these privileged pod creations due to missing enforcement labels on relevant namespaces.
References
- github.com/fission/fission/security/advisories/GHSA-gx55-f84r-v3r7 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-50564 (opens in a new tab)
- github.com/fission/fission/pull/3391 (opens in a new tab)
- github.com/fission/fission/commit/e484df8460bb4e8026e24210120602aa7f181f64 (opens in a new tab)
- github.com/fission/fission (opens in a new tab)
- github.com/fission/fission/releases/tag/v1.24.0 (opens in a new tab)