{"id":"CVE-2026-49824","title":"Fission: Cross-namespace Environment reference via unvalidated EnvironmentRef in Function admission webhook","summary":"Fission: Cross-namespace Environment reference via unvalidated EnvironmentRef in Function admission webhook","severity":"high","cvss":8.5,"cwe":["CWE-284","CWE-863"],"vendor":"fission","product":"github.com/fission/fission","ecosystem":"go","affected":["github.com/fission/fission <= 1.23.0"],"patched":["github.com/fission/fission 1.24.0"],"published":"2026-06-30","updated":"2026-06-30","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-cvw6-gfvv-953q","references":[{"url":"https://github.com/fission/fission/security/advisories/GHSA-cvw6-gfvv-953q"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49824"},{"url":"https://github.com/fission/fission/pull/3389"},{"url":"https://github.com/fission/fission/commit/80e7ba55228e1ef426f51353e25d2682ec61de34"},{"url":"https://github.com/fission/fission/releases/tag/v1.24.0"},{"url":"https://github.com/advisories/GHSA-cvw6-gfvv-953q"}],"tags":["ghsa","go"],"epss":0.00236,"epssPercentile":0.1487,"ingestedAt":"2026-06-30T21:24:14.411Z","slug":"CVE-2026-49824","body":"## Overview\n\n### Summary\n\nThe 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\n`spec.environment.namespace`.\n\n### Details\n\nAn 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\nfunction pods, so the attacker's function executed inside the victim's container image.\n\nThis 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.\n\n### Impact\n\nA 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.\n\n### Fix\n\nFixed in [#3389](https://github.com/fission/fission/pull/3389) and released in [v1.24.0](https://github.com/fission/fission/releases/tag/v1.24.0).\n\n- **Admission webhook** (`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).\n- **Controller belt-and-braces:** the same check runs before the cross-namespace `Environments(...).Get` in poolmgr `getFunctionEnv` and newdeploy `fnCreate` / `RefreshFuncPods`, covering webhook-bypass clusters (`failurePolicy=Ignore`)\nand stale Function objects from upgrade-before-restart windows.\n\n### Behavioural change\n\nFunctions that explicitly set `spec.environment.namespace` to a different namespace are now rejected at admission. Empty-string remains accepted.\n\n## Affected packages\n\n- `github.com/fission/fission <= 1.23.0`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `github.com/fission/fission 1.24.0`","depth":"twilight","depthScore":47,"depthScoreParts":{"impact":46.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}