Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance
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
A low-privilege developer who could create a KubernetesWatchTrigger (KWT) in their own namespace was able to establish a persistent surveillance channel over any other namespace.
Details
Two independent flaws compounded:
1. pkg/kubewatcher/kubewatcher.go::createKubernetesWatch used w.Spec.Namespace (user-controlled) directly as the Watch target without checking it against w.Namespace (the KWT's own namespace). kubewatcher established the Watch
using its cluster-scoped service account and serialized every Pod/Service/Job change event as full JSON over HTTP POST to the attacker's function.
2. The validating webhook (pkg/webhook/kuberneteswatchtrigger.go) registered verbs=create only, so update/patch requests bypassed validation entirely.
A separate leak: an empty spec.namespace resolved to all namespaces via the controller's default, letting an attacker omit the field to surveil the entire cluster.
Impact
A tenant with kuberneteswatchtriggers.fission.io/create could continuously receive full event payloads for Pods, Services, and Jobs in any namespace — a persistent cross-tenant surveillance channel requiring no additional privileges.
Fix
Fixed in #3379 and released in v1.24.0.
- The validating webhook marker is extended to
verbs=create;update. ValidaterejectsKubernetesWatchTrigger.spec.namespace != metadata.namespace.- A controller guard in
createKubernetesWatchrejects cross-namespace targets that bypass admission and coerces an emptySpec.Namespaceto the trigger's own namespace.
Behavioural change
KubernetesWatchTriggers with an unset spec.namespace now watch only their own namespace instead of all namespaces. Anyone relying on the previous all-namespaces behaviour must create a separate KWT per namespace.
Is GHSA-gc3j-79f2-7vvw 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-gc3j-79f2-7vvw
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-49822
- 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.