github.com/fission/fission
Affected
- introduced
0, fixed1.24.0(semver)
Fixed versions
1.24.0
Fix
- Fixed version
1.24.0go get github.com/fission/[email protected]
Advisory
Also known as: CVE-2026-49824, GO-2026-5852
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 onspec.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.
pkg/webhook/function.go::Validate) rejects Function.spec.environment.namespace != metadata.namespace. An empty namespace remains accepted (the CLI defaults it to the function's namespace).Environments(...).Get in poolmgr getFunctionEnv and newdeploy fnCreate / 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.
High Basis: The source's own band: HIGH
0, fixed 1.24.0 (semver)1.24.0
1.24.0go get github.com/fission/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0