← Back
CVE-2026-50545
critical
CVSS 9.9
Privilege Escalation in github.com/fission/fission (CVE-2026-50545)
Summary
vulnerability in github.com/fission/fission (CVE-2026-50545). Successful exploitation can lead to full system takeover. Exploitable via ``Environment.spec.runtime.podSpec``. Mitigation: upgrade to `1.24.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-50545** has been found in github.com/fission/fission.
Attackers can target a specific entry point like ``Environment.spec.runtime.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-50545" on the vendor's site.
CVE-2026-50545 (github.com/fission/fission) — CWE-269 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `Environment.spec.runtime.podSpec` / `spec.builder.podSpec` / `MergePodSpec` / `hostPID`
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 ``Environment.spec.runtime.podSpec`` without authentication.
📍 Affected scope
github.com/fission/fission — . Attack surface: `Environment.spec.runtime.podSpec` / `spec.builder.podSpec` / `MergePodSpec` / `hostPID`.
🔥 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/fission/fission to 1.24.0ステージング環境で 1.24.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/fission/fission
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.24.0"}]}]
References
- web https://github.com/fission/fission/pull/3390
- web https://github.com/fission/fission/pull/3391
- web https://github.com/fission/fission/releases/tag/v1.24.0
- web https://github.com/fission/fission/security/advisories/GHSA-wmgg-3p4h-48x7
- web https://nvd.nist.gov/vuln/detail/CVE-2026-50545
- web https://github.com/fission/fission/commit/8fa799417c77ce8a0189d9858bfe11ece29b84a6
- web https://github.com/fission/fission/commit/e484df8460bb4e8026e24210120602aa7f181f64
- web https://github.com/advisories/GHSA-wmgg-3p4h-48x7