Vulnerability in github.com/fission/fission (CVE-2026-50565)
Summary
Vulnerability in github.com/fission/fission (CVE-2026-50565). Confidential information can be exposed externally. Exploitable via Environment.spec.builder.image. Mitigation: upgrade to 1.24.0 or later.
Original description
The description as published by the source.
Summary
Fission builder pods were created with ServiceAccountName: fission-builder and no AutomountServiceAccountToken: false, so the kubelet auto-mounted the service-account token into every container in the pod — including the
user-supplied builder image.
Details
The user controls the builder container image, command, and podspec through Environment.spec.builder.image / .container / .podspec. With the SA token auto-mounted at /var/run/secrets/kubernetes.io/serviceaccount/token inside that
container, any code running there inherited the fission-builder identity. The fission-builder SA holds namespace-wide get on secrets and configmaps (pkg/utils/serviceaccount.go), so the user-controlled builder container
could read every Secret in the builder namespace by name.
This is the buildermgr sibling of GHSA-85g2-pmrx-r49q (CVE-2026-46617), whose fix suppressed the SA-token automount on function runtime pods but did not cover the structurally identical primitive in pkg/buildermgr/envwatcher.go.
Impact
A subject with create/update on Environment CRDs in a namespace observed by the buildermgr could read every Secret and ConfigMap in the builder namespace via the auto-mounted fission-builder token.
Fix
Fixed in #3390 and released in v1.24.0. In createBuilderDeployment:
- Set pod-level `AutomountServiceAccountToken=false…
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-50565 has been found in github.com/fission/fission.
Attackers can target a specific entry point like Environment.spec.builder.image over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 4.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-50565" on the vendor's site.
CVE-2026-50565 (github.com/fission/fission) — CWE-250 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: Environment.spec.builder.image / get / secrets / configmaps
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 Environment.spec.builder.image.
Check the vendor advisory for the affected versions of github.com/fission/fission. Attack surface: Environment.spec.builder.image / get / secrets / configmaps.
Severity: Medium (CVSS 4.9/10). Confidential information can be exposed externally.
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 nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com