CVE-2026-49822 is a high-severity missing authorization vulnerability in github.com/fission/fission (go), affecting versions <= 1.23.0. It is fixed in 1.24.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::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. 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. Validate rejects KubernetesWatchTrigger.spec.namespace != metadata.namespace. A controller guard in createKubernetesWatch rejects cross-namespace targets that bypass admission and coerces an empty Spec.Namespace to 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.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
CVE-2026-49822 has a CVSS score of 7.7 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.24.0). Upgrading removes the vulnerable code path.
go
github.com/fission/fission (<= 1.23.0)github.com/fission/fission → 1.24.0 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-49822 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-49822 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-49822 in your environment →Upgrade github.com/fission/fission to 1.24.0 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-49822 is a high-severity missing authorization vulnerability in github.com/fission/fission (go), affecting versions <= 1.23.0. It is fixed in 1.24.0. The application does not perform an authorization check before performing a sensitive operation.
CVE-2026-49822 has a CVSS score of 7.7 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/fission/fission (go) versions <= 1.23.0 is affected.
Yes. CVE-2026-49822 is fixed in 1.24.0. Upgrade to this version or later.
Whether CVE-2026-49822 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/fission/fission to 1.24.0 or later.