https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 08:27:49 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-326501 EUVD-2026-326501 https://cve.radiocsirt.org/vuln/euvd-2026-326501 https://cve.radiocsirt.org/vuln/fkie_cve-2026-49821 <p>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, Fission&#39;s buildermgr controller processed Package CRDs without verifying that Package.spec.environment.namespace matched Package.metadata.namespace. This issue has been patched in version 1.24.0.</p> <p>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, Fission&#39;s buildermgr controller processed Package CRDs without verifying that Package.spec.environment.namespace matched Package.metadata.namespace. This issue has been patched in version 1.24.0.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-49821 https://cve.radiocsirt.org/vuln/ghsa-vjhc-cf4p-72q4 <p><strong>Affected:</strong> Go: github.com/fission/fission</p> <p>### Summary</p> <p>Fission&#39;s `buildermgr` controller processed `Package` CRDs without verifying that `Package.spec.environment.namespace` matched `Package.metadata.namespace`.</p> <p>### Details</p> <p>An attacker with `packages.fission.io/create` in their own namespace could set `spec.environment.namespace` to any other tenant&#39;s namespace. The controller then used its high-privilege service account to fetch the Environment cross-namespace and dispatch the build command into the **victim namespace&#39;s** builder pod.</p> <p>The build command&#39;s stdout is written verbatim into `Package.status.buildlog`. By running malicious code through an npm `preinstall` lifecycle hook (or any equivalent build step), the attacker could read the victim namespace&#39;s `fission-builder` Bearer token from inside that builder pod and surface it through the build log — then use the leaked token to read every Secret and ConfigMap in the victim namespace.</p> <p>### Impact</p> <p>Cross-tenant compromise: a package author in one namespace could execute code inside another tenant&#39;s builder pod and exfiltrate that namespace&#39;s `fission-builder` service-account token, giving namespace-wide secret and configmap read in the victim namespace.</p> <p>### Fix</p> <p>Fixed in [#3379](https://github.com/fission/fission/pull/3379) and released in [v1.24.0](https://github.com/fission/fission/releases/tag/v1.24.0). Two checks in series:</p> <p>- **Admission webhook** (`pkg/webhook/package.go::Validate`) rejects `Package.spec.environment.namespace != Package.metadata.names…</p> <p><strong>Affected:</strong> Go: github.com/fission/fission</p> <p>### Summary</p> <p>Fission&#39;s `buildermgr` controller processed `Package` CRDs without verifying that `Package.spec.environment.namespace` matched `Package.metadata.namespace`.</p> <p>### Details</p> <p>An attacker with `packages.fission.io/create` in their own namespace could set `spec.environment.namespace` to any other tenant&#39;s namespace. The controller then used its high-privilege service account to fetch the Environment cross-namespace and dispatch the build command into the **victim namespace&#39;s** builder pod.</p> <p>The build command&#39;s stdout is written verbatim into `Package.status.buildlog`. By running malicious code through an npm `preinstall` lifecycle hook (or any equivalent build step), the attacker could read the victim namespace&#39;s `fission-builder` Bearer token from inside that builder pod and surface it through the build log — then use the leaked token to read every Secret and ConfigMap in the victim namespace.</p> <p>### Impact</p> <p>Cross-tenant compromise: a package author in one namespace could execute code inside another tenant&#39;s builder pod and exfiltrate that namespace&#39;s `fission-builder` service-account token, giving namespace-wide secret and configmap read in the victim namespace.</p> <p>### Fix</p> <p>Fixed in [#3379](https://github.com/fission/fission/pull/3379) and released in [v1.24.0](https://github.com/fission/fission/releases/tag/v1.24.0). Two checks in series:</p> <p>- **Admission webhook** (`pkg/webhook/package.go::Validate`) rejects `Package.spec.environment.namespace != Package.metadata.names…</p> https://cve.radiocsirt.org/vuln/ghsa-vjhc-cf4p-72q4