CVE-2026-46617: Fission privilege escalation via ServiceAccount token leakage in runtime pods

CVE-2026-46617 · Severity: high · CVSS 4 · Published 2026-06-10

Fission is a framework used to run serverless functions on Kubernetes. A security flaw allowed user-provided code to inherit high-level administrative permissions intended only for the system's internal components. This could allow an attacker to steal sensitive information, such as database passwords, encryption keys, and configuration data, from the entire Kubernetes namespace where the function is running.

Technologies: Fission, github.com/fission/fission (Go). Vendors: Fission, Go.

Quick answers

Is CVE-2026-46617 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46617 being exploited in the wild.
How severe is CVE-2026-46617?
High severity, with a CVSS score of 4, published 10 June 2026.
Which products and versions are affected?
Fission <= 1.22.0; github.com/fission/fission (Go) <= 1.22.0, SEMVER:introduced=0,fixed=1.23.0.
Is there a fix for CVE-2026-46617?
Yes. github.com/fission/fission (Go): upgrade to 1.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46617 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-46617?
Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/fission/fission (Go): upgrade to 1.23.0 or later
    go get github.com/fission/fission@v1.23.0

Technical details

Fission runtime pods (poolmgr and newdeploy backends) were configured with the 'fission-fetcher' ServiceAccount, which possesses namespace-wide 'get' permissions for secrets and configmaps. Because Kubernetes automounts the ServiceAccount token into all containers within a pod by default, user-supplied function code could access this token at /var/run/secrets/kubernetes.io/serviceaccount/token. This allowed functions to bypass the 'Function.spec.secrets' allowlist and query the Kubernetes API for any sensitive data in the namespace. The fix in version 1.23.0 disables the default automount and uses projected volumes to ensure the token is only available to the internal fetcher sidecar.

Affected products

  • Fission Fission <= 1.22.0

Identifiers

  • CVE-2026-46617
  • GHSA-85g2-pmrx-r49q
  • GO-2026-5241

Timeline

  • 2026-05-08: other: Pull request to fix the issue submitted
  • 2026-05-15: patched: Version 1.23.0 released
  • 2026-05-15: advisory: GitHub Security Advisory published
  • 2026-06-10: disclosed: CVE-2026-46617 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.