Vulnerability in github.com/fission/fission (CVE-2026-46617)
Summary
Vulnerability in github.com/fission/fission (CVE-2026-46617). Risk of unauthorized operations or information disclosure. Exploitable via get. 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, Fission runtime pods were created with ServiceAccountName: fission-fetcher, and the fission-fetcher ServiceAccount was granted namespace-wide get on secrets and configmaps (it needs that to load function code, env vars, and config). The runtime pod's automounted token was reachable from inside the user's function container at /var/run/secrets/kubernetes.io/serviceaccount/token, so user-supplied function code inherited the same Kubernetes API privileges and could read any secret or configmap in the function's namespace — far beyond the Function.spec.secrets allowlist that the function specification suggests. 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-46617 has been found in github.com/fission/fission.
Attackers can target a specific entry point like get over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
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-46617" on the vendor's site.
CVE-2026-46617 (github.com/fission/fission) — CWE-250
Attack surface: get / secrets / configmaps / Function.spec.secrets
Patched: 1.23.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 get.
Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: get / secrets / configmaps / Function.spec.secrets.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.23.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.23.0ステージング環境で 1.23.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