PT-2026-42687 · Fission · Fission

CVE-2026-46617

·

Published

2026-05-21

·

Updated

2026-07-30

CVSS v4.0

8.7

High

VectorAV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions Fission versions prior to 1.23.0
Description Runtime pods were configured with the fission-fetcher ServiceAccount, which possesses namespace-wide get permissions for secrets and configmaps. Because the service account token was automounted and accessible at /var/run/secrets/kubernetes.io/serviceaccount/token, user-supplied function code could inherit these privileges. This allows an attacker capable of deploying or updating a function to read all secrets (such as TLS keys, OIDC client secrets, and database credentials) and configmaps within the function's namespace, bypassing the restrictions defined in Function.spec.secrets.
Recommendations Update to version 1.23.0. Restrict permissions for creating or updating Function and Package Custom Resource Definitions (CRDs). Reduce the scope of the fission-fetcher ClusterRole or Role by constraining it to specific named secrets via separate Role bindings. Implement NetworkPolicy egress rules to deny function pods access to the Kubernetes API server.

Exploit

Fix

LPE

Improper Privilege Management

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-46617
GHSA-85G2-PMRX-R49Q
GO-2026-5241
OPENSUSE-SU-2026:21483-1

Affected Products

Fission