Vulnerability in github.com/fission/fission (CVE-2026-46612)
Summary
Vulnerability in github.com/fission/fission (CVE-2026-46612). Successful exploitation can lead to full system takeover. Exploitable via storagesvc. Mitigation: upgrade to 1.23.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.23.0, the Fission storagesvc component registers archive CRUD handlers (/v1/archive GET / POST / DELETE and /v1/archives list) directly on its HTTP router without performing any authentication or authorization. Any caller able to reach the storagesvc ClusterIP — including any other workload in the same Kubernetes cluster — could enumerate archive IDs, download archives belonging to other tenants, upload arbitrary archive content, and delete archives. This issue has been patched in version 1.23.0.
Source: GitHub Security Advisories (Global) 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-46612 has been found in github.com/fission/fission.
Attackers can target a specific entry point like storagesvc over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/fission/fission to 1.23.0 or later.
If unsure, ask your IT team or search "github.com/fission/fission CVE-2026-46612" on the vendor's site.
CVE-2026-46612 (github.com/fission/fission) — CWE-306 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: storagesvc / NetworkPolicy / ServiceStoragesvc
Patched: 1.23.0 — apply immediately
Workaround: set networkPolicy.: enabled
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-306) exists in github.com/fission/fission. Attackers reach the vulnerable code path via storagesvc.
Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: storagesvc / NetworkPolicy / ServiceStoragesvc.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.23.0.
Workaround: set networkPolicy.: enabled
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 temporary workaround mitigate
set networkPolicy.: enabledパッチが適用されるまでの応急処置として、set networkPolicy.: enabled を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade github.com/fission/fission to 1.23.0ステージング環境で 1.23.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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
- patch github.com
- web github.com
- web github.com