CVE-2026-46612: Github.com/fission/fission Fission StorageSvc /v1/archive Endpoint Exposes Vulnerability

HIGH
Advisory Identifier: GHSA-chf8-4hv6-8pg6
CVSS 8.8
CWE-306
Published
Advisory Summary

CVE-2026-46612 is a HIGH (CVSS 8.8) fission storagesvc /v1/archive endpoint exposes vulnerability (CWE-306: Missing Authentication for Critical Function) affecting Github.com/fission/fission libraries in the Go ecosystem. The issue involves fission storagesvc /v1/archive endpoint exposes unauthenticated crud over all function archives. Remediation is available by upgrading affected packages to version 1.23.0.

CVE-2026-46612 at a Glance

CVE Identifier CVE-2026-46612
GHSA Identifier GHSA-chf8-4hv6-8pg6
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-306: Missing Authentication for Critical Function
Affected Product Github.com/fission/fission
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-46612

To remediate this vulnerability, upgrade all affected Github.com/fission/fission dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/fission/fission fixed: 1.23.0
Upgrade github.com/fission/fission to 1.23.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/fission/fission

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-46612, inspect your project dependencies for Github.com/fission/fission:

inspect dependencies for github.com/fission/fission

Analyze the terminal output to locate any version of Github.com/fission/fission in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.23.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-306: Missing Authentication for Critical Function, where the product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. In Github.com/fission/fission, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: 1. Enumerate every function deployment archive in the cluster. 2. Download the deployment archive of any function in any namespace, exposing the function's source code and any embedded secrets. 3. Delete archives, causing the next function specialization or rebuild to fail. 4. 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](https://github.com/fission/fission/releases/tag/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) 1. Enable the Helm chart's per-service NetworkPolicy (set `networkPolicy.enabled=true`). 2. Restrict `storagesvc` egress/ingress to the executor, builder, and fetcher pods only. 3. Avoid running untrusted workloads in the cluster that hosts Fission.

CVE-2026-46612 Affected Github.com/fission/fission Versions

1 component(s)
Fixed Versions:
1.23.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/fission/fission
Go
< 1.23.0
1.23.0

References

Frequently Asked Questions

What is CVE-2026-46612?
CVE-2026-46612 is a security vulnerability in Github.com/fission/fission involving Fission StorageSvc /v1/archive endpoint exposes unauthenticated CRUD over all function archives under CWE-306: Missing Authentication for Critical Function.
Which Github.com/fission/fission versions are affected?
Affected versions include releases prior to 1.23.0 across affected packages: github.com/fission/fission.
What version fixes CVE-2026-46612?
Upgrading to 1.23.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/fission/fission affected?
Yes, github.com/fission/fission is affected in releases prior to 1.23.0. Upgrade your dependency to 1.23.0 or later.
What is the CVSS score of CVE-2026-46612?
CVE-2026-46612 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-46612?
CVE-2026-46612 is classified under CWE-306: Missing Authentication for Critical Function (The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.).
How can I check Go dependencies for CVE-2026-46612?
Run the dependency tree command: 'inspect dependencies for github.com/fission/fission'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-chf8-4hv6-8pg6",
  "modified" : "2026-07-21T13:58:59Z",
  "published" : "2026-05-21T20:07:13Z",
  "aliases" : [ "CVE-2026-46612" ],
  "summary" : "Fission StorageSvc /v1/archive endpoint exposes unauthenticated CRUD over all function archives",
  "details" : "### Summary\n\nThe 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.\n\n ### Affected component\n\n  - `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).\n\n ### Impact\n\nA 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:\n\n  1. Enumerate every function deployment archive in the cluster.\n  2. Download the deployment archive of any function in any namespace, exposing the function's source code and any embedded secrets.\n  3. Delete archives, causing the next function specialization or rebuild to fail.\n  4. Upload arbitrary archives that subsequent function specializations would fetch and execute.\n\nIn multi-tenant Fission deployments this completely breaks the tenant boundary for function code.\n\n  ### Root cause\n\n`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.\n\n  ### Fix\n\n  Released in [v1.23.0](https://github.com/fission/fission/releases/tag/v1.23.0):\n\n  - **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`.\n  - 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).\n\n  ### Mitigation (until upgrade)\n\n  1. Enable the Helm chart's per-service NetworkPolicy (set `networkPolicy.enabled=true`).\n  2. Restrict `storagesvc` egress/ingress to the executor, builder, and fetcher pods only.\n  3. Avoid running untrusted workloads in the cluster that hosts Fission.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fission/fission"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.23.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.22.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/security/advisories/GHSA-chf8-4hv6-8pg6"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46612"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/pull/3365"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/pull/3368"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fission/fission"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/releases/tag/v1.23.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-306" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-21T20:07:13Z",
    "nvd_published_at" : "2026-06-10T18:17:05Z"
  }
}