Is CVE-2026-46612 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-46612 being exploited in the wild.

How severe is CVE-2026-46612?

High severity, with a CVSS score of 8.8, published 10 June 2026.

Which products and versions are affected?

Fission < 1.23.0, <= 1.22.0; github.com/fission/fission (Go) <= 1.22.0, SEMVER:introduced=0,fixed=1.23.0.

Is there a fix for CVE-2026-46612?

Yes. github.com/fission/fission (Go): upgrade to 1.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-46612 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-46612?

Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46612: Fission missing authentication in storagesvc archive handlers

Q: Which products and versions are affected?

Fission < 1.23.0, <= 1.22.0; github.com/fission/fission (Go) <= 1.22.0, SEMVER:introduced=0,fixed=1.23.0.

Q: Is there a fix for CVE-2026-46612?

Yes. github.com/fission/fission (Go): upgrade to 1.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-46612 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-46612?

Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-46612 · Severity: high · CVSS 8.8 · Published 2026-06-10

Fission is a serverless framework that allows developers to run code functions on Kubernetes clusters. A security flaw in the storage component allowed any user or application within the same network to access, download, or delete private code archives without any authentication. This could lead to the theft of proprietary source code or the disruption of applications by deleting their underlying functions.

Technologies: Fission, github.com/fission/fission (Go). Vendors: Fission, Go.

Quick answers

Is CVE-2026-46612 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-46612 being exploited in the wild.
How severe is CVE-2026-46612?: High severity, with a CVSS score of 8.8, published 10 June 2026.
Which products and versions are affected?: Fission < 1.23.0, <= 1.22.0; github.com/fission/fission (Go) <= 1.22.0, SEMVER:introduced=0,fixed=1.23.0.
Is there a fix for CVE-2026-46612?: Yes. github.com/fission/fission (Go): upgrade to 1.23.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46612 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-46612?: Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fission/fission (Go): upgrade to 1.23.0 or later
```
go get github.com/fission/fission@v1.23.0
```

Technical details

The Fission 'storagesvc' component fails to implement authentication or authorization middleware for its archive CRUD handlers (/v1/archive and /v1/archives). An attacker with network access to the storagesvc ClusterIP—such as a compromised workload in the same Kubernetes cluster—can enumerate archive IDs, download archives belonging to other tenants, upload arbitrary content, or delete existing archives. The vulnerability stems from the component registering these handlers directly on its HTTP router without security checks (CWE-306). The issue is addressed in version 1.23.0 by introducing HMAC-SHA256 application-layer authentication and providing opt-in Kubernetes NetworkPolicies to restrict traffic.

Affected products

Fission Fission < 1.23.0

Identifiers

CVE-2026-46612
GHSA-chf8-4hv6-8pg6
GO-2026-5323

Timeline

2026-05-07: other: NetworkPolicy mitigation merged
2026-05-09: other: HMAC authentication implementation merged
2026-05-15: patched: Version 1.23.0 released
2026-06-10: disclosed: CVE-2026-46612 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.