EUVD-2026-36102
GHSA-m63v-2g9w-2w6v
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 VectorVendor: GitHub_M
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
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, a tenant with environments.fission.io create/update RBAC can run privileged / allowPrivilegeEscalation / dangerous-capability containers in the Fission function or builder namespace, scheduled under the executor's high-privilege service account - enabling container-sandbox escape, host filesystem and network access, and potential node- and cluster-level compromise. This issue has been patched in version 1.24.0.
Articles & Coverage 2
AnalysisAI
Privilege escalation in Fission prior to version 1.24.0 allows a tenant holding environments.fission.io create/update RBAC to define Environment custom resources with privileged, allowPrivilegeEscalation, or dangerous Linux capabilities on the bare Runtime.Container or Builder.Container fields, which bypass the existing PodSpec safety validator and get scheduled under the executor's high-privilege service account. Successful abuse enables container-sandbox escape, host filesystem and network access, and node- or cluster-level compromise. No public exploit identified at time of analysis, but the upstream fix is published in v1.24.0.
Technical ContextAI
Fission is a Kubernetes-native serverless framework whose Environment CRD exposes spec.runtime.container and spec.builder.container as bare apiv1.Container objects that are merged into runtime/builder pods. The pre-fix ValidatePodSpecSafety in pkg/apis/core/v1/podspec_safety.go only walked PodSpec.Containers and InitContainers, so the standalone Container fields on the Environment CRD were never inspected, leaving SecurityContext.Privileged, AllowPrivilegeEscalation, and Capabilities.Add unchecked. This is a CWE-250 (Execution with Unnecessary Privileges) class flaw: the executor-managed pod runs under a high-privilege service account, so unsafe containers attached via Environment effectively inherit cluster-administrative reach. The patch introduces a standalone ValidateContainerSafety helper invoked both from the PodSpec walker and directly from Environment.Validate to close the bypass (PR #3406, closing GHSA-m63v-2g9w-2w6v).
RemediationAI
Vendor-released patch: upgrade Fission to version 1.24.0 or later, which adds ValidateContainerSafety enforcement against Environment.spec.runtime.container and spec.builder.container (see https://github.com/fission/fission/releases/tag/v1.24.0 and PR https://github.com/fission/fission/pull/3406). Where immediate upgrade is not possible, restrict the environments.fission.io create/update verbs in Roles/ClusterRoles to trusted platform operators only and remove this RBAC from tenant namespaces, accepting that tenants will lose self-service Environment management. As an additional compensating control, enforce a cluster-wide admission policy (Kyverno, OPA Gatekeeper, or Pod Security Admission acting on the Fission function/builder namespaces) that rejects pods with securityContext.privileged=true, allowPrivilegeEscalation=true, or dangerous capabilities such as SYS_ADMIN and NET_ADMIN; this adds latency and may break legitimate Environments that rely on elevated capabilities but blocks the bypass even without the upstream patch. Full advisory details are available at https://github.com/fission/fission/security/advisories/GHSA-m63v-2g9w-2w6v.
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-250 – Execution with Unnecessary Privileges
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