Fission StorageSvc Unauthenticated Archive CRUD Vulnerability
The Fission `storagesvc` component exposes unauthenticated CRUD operations on the `/v1/archive` endpoint, allowing any workload within the same Kubernetes cluster to enumerate archive IDs, download archives, upload arbitrary content, and delete archives, leading to potential code and secret exposure and function disruption.
Fission is a serverless framework for Kubernetes. A critical vulnerability exists within the storagesvc component of Fission versions 1.22.0 and earlier. The storagesvc registers archive CRUD handlers (/v1/archive GET / POST / DELETE and /v1/archives list) directly on its HTTP router without any authentication or authorization checks. This oversight enables any workload within the same Kubernetes cluster to interact with the archive storage service, bypassing tenant boundaries. The vulnerability was addressed in Fission v1.23.0 via PR #3368, which implemented HMAC verification, and defense in depth was added via PR #3365 which implemented a NetworkPolicy for the service. This unauthenticated access allows attackers to enumerate, download, modify, or delete function deployment archives, impacting code integrity and confidentiality.
Attack Chain
- An attacker compromises a pod within the Kubernetes cluster hosting Fission.
- The compromised pod discovers the
storagesvcClusterIP. - The attacker sends an unauthenticated GET request to
/v1/archivesto enumerate archive IDs. - The attacker crafts a GET request to
/v1/archive/{archiveID}to download a function’s deployment archive, exposing source code and embedded secrets. - Alternatively, the attacker sends a DELETE request to
/v1/archive/{archiveID}to remove a function archive, causing function specialization failures. - The attacker can also send a POST request to
/v1/archiveto upload a malicious archive. - Subsequent function specializations fetch and execute the uploaded malicious archive.
- The attacker achieves arbitrary code execution within the Fission environment, potentially leading to further compromise.
Impact
Successful exploitation allows a workload within the cluster to enumerate every function deployment archive, download sensitive function code and secrets, delete archives causing function failures, and upload malicious archives leading to code execution. This completely breaks tenant boundaries in multi-tenant Fission deployments. The absence of authentication on the storagesvc endpoint allows for trivial exploitation from any compromised workload within the cluster. This vulnerability is tracked as CVE-2026-46612.
Recommendation
- Upgrade Fission to v1.23.0 or later to incorporate the authentication fix introduced in PR #3368.
- Enable the Helm chart’s per-service NetworkPolicy (set
networkPolicy.enabled=true) as outlined in the Mitigation section of the advisory. - Implement egress/ingress restrictions for
storagesvcto limit network access to only the executor, builder, and fetcher pods, as described in the advisory. - Deploy the Sigma rule “Detect Unauthenticated Access to Fission StorageSvc Archive Endpoint” to detect unauthorized access attempts to the
/v1/archiveendpoint. - Deploy the Sigma rule “Detect Fission StorageSvc Archive Manipulation” to detect POST/DELETE attempts to the
/v1/archiveendpoint.
Detection coverage 2
Detect Unauthenticated Access to Fission StorageSvc Archive Endpoint
highDetects unauthenticated GET requests to the Fission StorageSvc archive endpoints (`/v1/archives`, `/v1/archive/{archiveID}`), indicating potential unauthorized access. This rule detects the enumeration or download of function deployment archives (CVE-2026-46612).
Detect Fission StorageSvc Archive Manipulation
highDetects unauthenticated POST or DELETE requests to the Fission StorageSvc `/v1/archive` endpoint, indicating potential manipulation of function deployment archives (CVE-2026-46612).
Detection queries are available on the platform. Get full rules →