CVE-2026-46612 is a high-severity missing authentication for critical function vulnerability in github.com/fission/fission (go), affecting versions <= 1.22.0. It is fixed in 1.23.0.
Summary The Fission storagesvc component registers archive CRUD handlers (/v1/archive GET / POST / DELETE and /v1/archives list) directly on its HTTP router without performing any authentication or authorization. Any caller able to reach the storagesvc ClusterIP, including any other workload in the same Kubernetes cluster, could enumerate archive IDs, download archives belonging to other tenants, upload arbitrary archive content, and delete archives. ### Affected component pkg/storagesvc/storagesvc.go, handler registration and per-route handler logic at lines 72-95 (list), 167-199 (download/delete), and 263-270 (route wiring). ### Impact A workload elsewhere in the cluster (e.g. a compromised function pod, a noisy-neighbour tenant in a multi-tenant deployment, or any pod whose egress is not constrained by NetworkPolicy) could: Enumerate every function deployment archive in the cluster. Download the deployment archive of any function in any namespace, exposing the function's source code and any embedded secrets. Delete archives, causing the next function specialization or rebuild to fail. Upload arbitrary archives that subsequent function specializations would fetch and execute. In multi-tenant Fission deployments this completely breaks the tenant boundary for function code. ### Root cause pkg/storagesvc/storagesvc.go mounts the handlers without an authentication middleware. Network-layer controls (NetworkPolicy) were the only line of defence before this fix, and the chart shipped no NetworkPolicy for storagesvc by default, so reachability was open. ### Fix Released in v1.23.0: PR #3368 (commit 2455fc0c) wraps the storagesvc archive routes with the application-layer HMAC verifier from pkg/auth/hmac using the ServiceStoragesvc derived key. Callers (executor, fetcher, builder, CLI) sign their requests using a shared cluster master secret derived per-service via HKDF. Mismatched signatures are rejected with 401. Defence in depth: PR #3365 added a NetworkPolicy for storagesvc so only the executor/fetcher/builder pods can reach it network-layer (independent of authentication). ### Mitigation (until upgrade) Enable the Helm chart's per-service NetworkPolicy (set networkPolicy.enabled=true). Restrict storagesvc egress/ingress to the executor, builder, and fetcher pods only. Avoid running untrusted workloads in the cluster that hosts Fission.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2026-46612 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.23.0). Upgrading removes the vulnerable code path.
go
github.com/fission/fission (<= 1.22.0)github.com/fission/fission → 1.23.0 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-46612 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-46612 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-46612 in your environment →Upgrade github.com/fission/fission to 1.23.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-46612 is a high-severity missing authentication for critical function vulnerability in github.com/fission/fission (go), affecting versions <= 1.22.0. It is fixed in 1.23.0. A critical operation is accessible without requiring any authentication.
CVE-2026-46612 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/fission/fission (go) versions <= 1.22.0 is affected.
Yes. CVE-2026-46612 is fixed in 1.23.0. Upgrade to this version or later.
Whether CVE-2026-46612 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/fission/fission to 1.23.0 or later.