Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- High severity, with a CVSS score of 8.1, published 30 June 2026.
- Which products and versions are affected?
- Fission <= 1.23.0; github.com/fission/fission (Go) <= 1.23.0.
- Is there a fix for This vulnerability?
- A patch was published on 2026-06-30: Fixed in v1.24.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- 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.
Technical details
The Fission MessageQueueTrigger (MQT) scaler controller contains two privilege escalation primitives. First, the 'getEnvVarlist' function in 'pkg/mqtrigger/scalermanager.go' materialized Secret values into plaintext environment variables within Deployment pod templates, allowing users without 'secrets/get' RBAC to exfiltrate any Secret in the namespace. Second, the 'util.MergePodSpec' function lacked an allowlist, permitting users to inject arbitrary fields into the connector PodSpec, including container images, commands, and service accounts. An attacker with 'messagequeuetriggers/create' permissions can exploit these to escalate privileges to 'deployments/create' or read sensitive data. The issues are fixed in version 1.24.0 by using 'SecretKeyRef' for environment variables and implementing a strict PodSpec field allowlist.
Affected products
- fission fission <= 1.23.0
Timeline
- 2026-05-26: disclosed
- 2026-06-30: advisory
- 2026-06-30: patched: Fixed in v1.24.0