Fission StorageSvc /v1/archive endpoint exposes unauthenticated CRUD over all function archives

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-46612: 0.34% estimated exploitation activity in the next 30 days; percentile 28.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

21 May 2026, 20:07 UTC

Last modified by the source

10 Jun 2026, 18:41 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-chf8-4hv6-8pg6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46612

Advisory: Fission StorageSvc /v1/archive endpoint exposes unauthenticated CRUD over all function archives
IDs: CVE-2026-46612, GHSA-chf8-4hv6-8pg6
Record: https://patchnext.com/advisories/cve-2026-46612 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fission/fission 1.23.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fission/fission: affected <= 1.22.0; fixed in 1.23.0

## Suggested inspection (read-only)
- Go github.com/fission/fission: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fission/fission.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-chf8-4hv6-8pg6 (GitHub-reviewed advisory GHSA-chf8-4hv6-8pg6 lists affected ranges: Go github.com/fission/fission >=0 <=1.22.0)

Commands are suggestions: review each one before running it.