Vulnerability in github.com/fission/fission (CVE-2026-50566)
Summary
Vulnerability in github.com/fission/fission (CVE-2026-50566). Successful exploitation can lead to full system takeover. Exploitable via PodSpec. Mitigation: upgrade to 1.24.0 or later.
Original description
The description as published by the source.
Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, a tenant with environments.fission.io create/update RBAC can run privileged / allowPrivilegeEscalation / dangerous-capability containers in the Fission function or builder namespace, scheduled under the executor's high-privilege service account — enabling container-sandbox escape, host filesystem and network access, and potential node- and cluster-level compromise. This issue has been patched in version 1.24.0.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50566 has been found in github.com/fission/fission.
Attackers can target a specific entry point like PodSpec over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/fission/fission to 1.24.0 or later.
If unsure, ask your IT team or search "github.com/fission/fission CVE-2026-50566" on the vendor's site.
CVE-2026-50566 (github.com/fission/fission) — CWE-250 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: PodSpec / spec.runtime.podSpec / spec.builder.podSpec / function.spec.podSpec
Patched: 1.24.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-250) exists in github.com/fission/fission. Attackers reach the vulnerable code path via PodSpec.
Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: PodSpec / spec.runtime.podSpec / spec.builder.podSpec / function.spec.podSpec.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 1.24.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/fission/fission' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/fission/fission' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/fission/fissionを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/fission/fission to 1.24.0ステージング環境で 1.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com
- web github.com
- web github.com