Fission: Cross-namespace Environment reference in Package allows build-time command execution and SA token exfiltration
Published 30 Jun 2026 · Updated 7 Jul 2026
Is your project on an affected github.com/fission/fission?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <1.24.0
- Fixed in
- 1.24.0
go get github.com/fission/fission@v1.24.0Details
Summary
Fission's buildermgr controller processed Package CRDs without verifying that Package.spec.environment.namespace matched Package.metadata.namespace.
Details
An attacker with packages.fission.io/create in their own namespace could set spec.environment.namespace to any other tenant'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's builder pod.
The build command'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'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.
Impact
Cross-tenant compromise: a package author in one namespace could execute code inside another tenant's builder pod and exfiltrate that namespace's fission-builder service-account token, giving namespace-wide secret and configmap read in
the victim namespace.
Fix
Fixed in #3379 and released in v1.24.0. Two checks in series:
- Admission webhook (
pkg/webhook/package.go::Validate) rejectsPackage.spec.environment.namespace != Package.metadata.namespace. An empty namespace is still accepted; the controllers default it to the package's own namespace. - Controller belt-and-braces: the same check is repeated in
pkg/buildermgr/pkgwatcher.go::buildandpkg/buildermgr/common.go::buildPackagebefore the cross-namespaceEnvironments(...).Getcall, so a stale Package CR or a
webhook-bypass cluster (failurePolicy=Ignore) cannot exploit the primitive either.
Behavioural change
Packages that explicitly set spec.environment.namespace to a different namespace are now rejected at admission. Empty-string remains accepted (resolves to the package's own namespace, the same as the prior implicit behaviour).
Is GHSA-vjhc-cf4p-72q4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fission/fission, and gives you the command that fixes it.
More advisories for github.com/fission/fission
- LowCVE-2026-50567Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory in github.com/fission/fission · 18 Aug 2026
- LowCVE-2026-50570Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption in github.com/fission/fission · 18 Aug 2026
- LowCVE-2026-50568Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape in github.com/fission/fission · 18 Aug 2026
- LowCVE-2026-50569Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks in github.com/fission/fission · 18 Aug 2026
- LowCVE-2026-50568Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape · 28 Jul 2026
- HighCVE-2026-50567 Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory · 28 Jul 2026
References
- Linkgithub.com/fission/fission/security/advisories/GHSA-vjhc-cf4p-72q4
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-49821
- Linkgithub.com/fission/fission/pull/3379
- Linkgithub.com/fission/fission/commit/e2b92663499f4dc3a1e2d38178f39c3c65e0134a
- Packagegithub.com/fission/fission
- Linkgithub.com/fission/fission/releases/tag/v1.24.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.