CVE-2026-49822: Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance
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.
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 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:
pkg/kubewatcher/kubewatcher.go::createKubernetesWatchusedw.Spec.Namespace(user-controlled) directly as the Watch target without checking it againstw.Namespace(the KWT's own namespace).kubewatcherestablished 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.
- The validating webhook (
pkg/webhook/kuberneteswatchtrigger.go) registeredverbs=createonly, soupdate/patchrequests 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.
Credited to j311yl0v3u, b0b0haha, sanketsudake.
References
- https://github.com/fission/fission/security/advisories/GHSA-gc3j-79f2-7vvw
- https://nvd.nist.gov/vuln/detail/CVE-2026-49822
- https://github.com/fission/fission/pull/3379
- https://github.com/fission/fission/commit/e2b92663499f4dc3a1e2d38178f39c3c65e0134a
- https://github.com/fission/fission/releases/tag/v1.24.0
- https://github.com/advisories/GHSA-gc3j-79f2-7vvw
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-49823
Fission: Cross-namespace Package read via unvalidated PackageRef in Function admission webhook
high7.7Jun 30, 2026
