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

High 8.7 Published Updated

User function code inherits fetcher service account privileges, allowing unauthorized reading of all secrets and configmaps in the namespace.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-46617?

CVE-2026-46617 is a high-severity vulnerability in fission, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-538, CWE-269, CWE-250

Which versions are affected by CVE-2026-46617?

3 open source packages ship an affected version, including github.com/fission/fission.

PackageAffectedFixed in
github.com/fission/fission GoAll versions1.23.0
github.com/fission/fission GoAll versions1.23.0
github.com/fission/fission GoAll versions1.23.0

How do I fix CVE-2026-46617?

Upgrade github.com/fission/fission to 1.23.0 or later.

Is CVE-2026-46617 being exploited?

There is no known exploitation of CVE-2026-46617 in the wild and no public exploit code.

Sources

Also known as GHSA-85g2-pmrx-r49q, GO-2026-5241.

Is CVE-2026-46617 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free