EUVD-2026-36098
GHSA-wmgg-3p4h-48x7
Severity by source
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Primary rating from Vendor (GitHub_M).
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionNVD
Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, the Environment.spec.runtime.podSpec / spec.builder.podSpec passthrough lacked validation, and MergePodSpec propagated dangerous fields into the generated pods. This issue has been patched in version 1.24.0.
Articles & Coverage 2
AnalysisAI
Privilege escalation in Fission prior to 1.24.0 allows an authenticated user with permission to create or modify Environment custom resources to abuse unvalidated podSpec passthrough fields (Environment.spec.runtime.podSpec and spec.builder.podSpec), causing MergePodSpec to propagate dangerous fields - notably AutomountServiceAccountToken - into the generated builder/runtime pods. Because the fission-builder ServiceAccount token then becomes accessible from a user-supplied container, an attacker can pivot from a Fission tenant into broader Kubernetes cluster privileges (CVSS 9.9, Scope:Changed). No public exploit identified at time of analysis.
Technical ContextAI
Fission is a Kubernetes-native serverless platform whose controllers materialize Environment CRDs into Deployments for builder and runtime pods. The Environment API exposes a podSpec passthrough so operators can tune the generated pods; internally a helper called MergePodSpec overlays the user-supplied PodSpec onto the controller's base PodSpec. CWE-269 (Improper Privilege Management) applies because the merge propagated security-critical fields without validation or re-clamping - in particular AutomountServiceAccountToken, which controls whether the kubelet injects the pod's ServiceAccount token at /var/run/secrets/kubernetes.io/serviceaccount into every container. The fission-builder ServiceAccount is intended to be consumed only by the fetcher sidecar (via an explicit projected volume), but the unvalidated merge could re-enable auto-mount on the user-controlled builder container, exposing the SA token to attacker-supplied code. Affected CPE: cpe:2.3:a:fission:fission:*:*:*:*:*:*:*:* prior to v1.24.0.
RemediationAI
Upgrade to Fission v1.24.0 or later (release: https://github.com/fission/fission/releases/tag/v1.24.0), which corresponds to the upstream fix in PRs https://github.com/fission/fission/pull/3390 and https://github.com/fission/fission/pull/3391 - these explicitly set AutomountServiceAccountToken=false on the pod, re-clamp it after MergePodSpec runs, and re-mount the fission-builder SA token only on the fetcher sidecar via a projected volume. If immediate upgrade is not possible, the highest-leverage compensating control is to restrict Kubernetes RBAC so that only trusted operators can create or update Environment resources (verbs create/update/patch on environments.fission.io) - this removes the attacker's entry point at the cost of breaking self-service Environment management for tenants. As a secondary hardening step, scope the fission-builder ServiceAccount's RoleBindings/ClusterRoleBindings to the minimum required (least-privilege) so that token theft yields less, and consider a validating admission webhook (e.g. Kyverno/Gatekeeper) that rejects Environment objects whose podSpec passthrough sets AutomountServiceAccountToken, serviceAccountName, hostPath volumes, hostNetwork/hostPID, or privileged securityContext. Consult the advisory at https://github.com/fission/fission/security/advisories/GHSA-wmgg-3p4h-48x7 for vendor guidance.
More in Kubernetes
View allA critical vulnerability in Kubernetes ingress-nginx controller allows unauthenticated attackers with pod network access
Credential-harvesting malware compromised 84 versions of 42 TanStack npm packages on 2026-05-11 via chained GitHub Actio
Kubernetes ingress-nginx contains a configuration injection vulnerability via the mirror-target and mirror-host Ingress
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-url` Ingres
A security issue was discovered in ingress-nginx https://github.com/kubernetes/ingress-nginx where the `auth-tls-match-c
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.exter
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Rated critical severity (CVSS 9.9), this vulne
The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4
Fluentd configuration injection in the kube-logging Logging operator before 6.6.0 allows a namespace-scoped user who can
Kyverno Kubernetes policy engine prior to 1.x has a privilege escalation vulnerability (CVSS 9.9) allowing policy bypass
Kamaji is the Hosted Control Plane Manager for Kubernetes. Rated critical severity (CVSS 9.9), this vulnerability is rem
Jumpserver is a popular open source bastion host, and Koko is a Jumpserver component that is the Go version of coco, ref
Same weakness CWE-269 – Improper Privilege Management
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today