CVE 8.7 HIGH

Fission runtime pods automount the fission-fetcher service-account token into the user function container, granting function code namespace-wide secret / configmap read_CVE-2026-46617

8.7 / 10
HIGH
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Description

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.

AI Analysis

Fission runtime pods are vulnerable to namespace-wide secret and configmap read due to the automounted token, allowing user-supplied function code to inherit Kubernetes API privileges.

Basic Information

ID CVE-2026-46617
Source GitHub_M
Published Jun 10, 2026 at 17:20
Modified Jun 10, 2026 at 18:20

Affected Product

Vendor fission
Product fission
Version < 1.23.0
Affected Versions fission fission < 1.23.0

CWE Classification

AI Assessment

AI Score 8.7 / 10
AI Severity High
Vendor Platform9
Product Fission
Version < 1.23.0

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.