CVE-2026-49824: Fission: Cross-namespace Environment reference via unvalidated EnvironmentRef in Function admission webhook
Summary The Fission Function admission webhook (pkg/webhook/function.go) validated that spec.secrets[].namespace and spec.configmaps[].namespace equalled the function's own namespace but performed no equivalent check on spec.environment.namespace. Details An attacker with permission to create Functions in their own namespace could set spec.environment.namespace to any other tenant's namespace.
Published Jun 30, 2026
Affected packages
github.com/fission/fission
- Ecosystem
- Go
- Affected
- <= 1.23.0
- Fixed in
- 1.24.0
- Check
go list -m github.com/fission/fission
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
The Fission Function admission webhook (pkg/webhook/function.go) validated that spec.secrets[].namespace and spec.configmaps[].namespace equalled the function's own namespace but performed no equivalent check on spec.environment.namespace.
Details
An attacker with permission to create Functions in their own namespace could set spec.environment.namespace to any other tenant's namespace. poolmgr and newdeploy would then look up and use the victim's Environment CRD when scheduling function pods, so the attacker's function executed inside the victim's container image.
This is useful both for code and credential theft — the victim's runtime image may contain hardcoded secrets — and for confused-deputy attacks where the victim's runtime image is a privileged sidecar.
Impact
A tenant with functions.fission.io/create could run their own function code inside another tenant's container image, breaking the namespace trust boundary that the Function specification implies.
Fix
Fixed in #3389 and released in v1.24.0.
- Admission webhook (
pkg/webhook/function.go::Validate) rejectsFunction.spec.environment.namespace != metadata.namespace. An empty namespace remains accepted (the CLI defaults it to the function's namespace). - Controller belt-and-braces: the same check runs before the cross-namespace
Environments(...).Getin poolmgrgetFunctionEnvand newdeployfnCreate/RefreshFuncPods, covering webhook-bypass clusters (failurePolicy=Ignore)
and stale Function objects from upgrade-before-restart windows.
Behavioural change
Functions that explicitly set spec.environment.namespace to a different namespace are now rejected at admission. Empty-string remains accepted.
Credited to j311yl0v3u, b0b0haha, sanketsudake.
References
- https://github.com/fission/fission/security/advisories/GHSA-cvw6-gfvv-953q
- https://nvd.nist.gov/vuln/detail/CVE-2026-49824
- https://github.com/fission/fission/pull/3389
- https://github.com/fission/fission/commit/80e7ba55228e1ef426f51353e25d2682ec61de34
- https://github.com/fission/fission/releases/tag/v1.24.0
- https://github.com/advisories/GHSA-cvw6-gfvv-953q
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-50567
Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory
high7.7Jul 28, 2026CVE-2026-50568
Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape
low3.6Jul 28, 2026CVE-2026-50569
Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks
medium4.3Jul 28, 2026CVE-2026-50570
Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption
high8.5Jul 28, 2026CVE-2026-49821
Fission: Cross-namespace Environment reference in Package allows build-time command execution and SA token exfiltration
high7.7Jun 30, 2026CVE-2026-49822
Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance
high7.7Jun 30, 2026
