Categories
CVE-2026-50563 critical CVSS 9.9

Privilege Escalation in github.com/fission/fission (CVE-2026-50563)

Summary

Vulnerability in github.com/fission/fission (CVE-2026-50563). Successful exploitation can lead to full system takeover. Exploitable via Function.spec.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, Fission's Container Executor path lets a tenant supply Function.spec.podspec directly; the executor merges it into the executor-built podspec and creates a Deployment whose pods run the user's container image. 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-50563 has been found in github.com/fission/fission.
Attackers can target a specific entry point like Function.spec.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-50563" on the vendor's site.

CVE-2026-50563 (github.com/fission/fission) — CWE-269 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Function.spec.podspec / spec.PodSpec / hostPID / hostNetwork
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.

❓ What is the problem

A vulnerability (CWE-269) exists in github.com/fission/fission. Attackers reach the vulnerable code path via Function.spec.podspec.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: Function.spec.podspec / spec.PodSpec / hostPID / hostNetwork.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.24.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/fission/fission to 1.24.0

    ステージング環境で 1.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/fission/fission
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.24.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details