CVE-2026-49823: Fission: Cross-namespace Package read via unvalidated PackageRef in Function admission webhook
Summary A Fission Function spec carries three reference types — Secret, ConfigMap, and Package. The first two were namespace-validated by the admission webhook; PackageRef.Namespace was not. Details A tenant with functions.fission.io/create in their own namespace could set spec.package.packageref.namespace to any other 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
A Fission Function spec carries three reference types — Secret, ConfigMap, and Package. The first two were namespace-validated by the admission webhook; PackageRef.Namespace was not.
Details
A tenant with functions.fission.io/create in their own namespace could set spec.package.packageref.namespace to any other namespace. When the function is invoked, the fetcher sidecar reads the victim Package using the fission-fetcher service account's namespace-wide get packages permission and writes its contents to /userfunc/deployarchive inside the attacker's pool pod, exposing the victim's source code and any embedded credentials.
The fission-fetcher SA holds get packages in every configured function namespace (granted by charts/fission-all/templates/_function-access-role.tpl), so the namespace check was the only barrier between the attacker and any in-cluster Fission Package.
Impact
A function author in one namespace could read the deployment archive — and therefore the source code and embedded secrets — of any Package in any other namespace.
Fix
Fixed in #3389 and released in v1.24.0.
The admission webhook (pkg/webhook/function.go::Validate) rejects Function.spec.package.packageref.namespace != metadata.namespace. An empty namespace remains accepted (controllers default it to the function's namespace). This shipped together with the EnvironmentRef cross-namespace check (GHSA-cvw6-gfvv-953q).
Behavioural change
Functions that explicitly set spec.package.packageref.namespace to a different namespace are now rejected at admission.
Credited to j311yl0v3u, b0b0haha, sanketsudake.
References
- https://github.com/fission/fission/security/advisories/GHSA-3r8v-2xmj-5c39
- https://nvd.nist.gov/vuln/detail/CVE-2026-49823
- 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-3r8v-2xmj-5c39
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
