Skip to main content
VulnerabilityPublished

CVE-2026-49822: Fission · Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance

Affects github.com/fission/fissionSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 1.24.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.24.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade github.com/fission/fission to 1.24.0.

Affected software

ProductAffectedFixed in
Gogithub.com/fission/fissionAffected
  • <1.24.0
Fixed in
  • 1.24.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Fission version 1.24.0. Users should upgrade to v1.24.0 or later to apply the official fix. The fix includes enhanced webhook validation for create and update operations, strict enforcement that spec.namespace matches the trigger's namespace, and defaulting empty spec.namespace to the trigger's own namespace. No additional mitigation is required once upgraded. For users relying on the previous behavior where an unset spec.namespace watched all namespaces, separate KubernetesWatchTriggers per namespace must now be created.

Description

A vulnerability in Fission's KubernetesWatchTrigger (KWT) allowed a low-privilege developer to create triggers in their own namespace that could watch events across all namespaces, enabling persistent cross-namespace surveillance. The issue arose from improper validation of the spec.namespace field and insufficient webhook validation on update operations. This allowed attackers to receive full event payloads for Pods, Services, and Jobs cluster-wide without additional privileges. The vulnerability was fixed in version 1.24.0 by enforcing namespace validation and extending webhook checks.

References

Community reviews

Loading reviews…