# 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

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

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-85g2-pmrx-r49q, GO-2026-5241

## 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 (Insertion of Sensitive Information into Externally-Accessible File or Directory), CWE-269 (Improper Privilege Management), CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2026-46617?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fission/fission` | Go | All versions | 1.23.0 |
| `github.com/fission/fission` | Go | All versions | 1.23.0 |
| `github.com/fission/fission` | Go | All versions | 1.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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46617 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-46617 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fission/fission (Go): affected all versions; fixed in 1.23.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.23.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.23.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46617/ (Markdown: https://insights.sbomify.com/CVE-2026-46617/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46617
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46617
- OSV: https://osv.dev/vulnerability/CVE-2026-46617

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46617/
Summaries are generated and may contain mistakes; the official description above is the record.