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


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-gc3j-79f2-7vvw, GO-2026-5854

## What is CVE-2026-49822?

CVE-2026-49822 is a high-severity vulnerability in fission, published on 10 Jun 2026. 

### Official description

Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.24.0, 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. This issue has been patched in version 1.24.0.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-49822?

3 open source packages ship an affected version, including github.com/fission/fission.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/fission/fission` | Go | All versions | 1.24.0 |
| `github.com/fission/fission` | Go | All versions | 1.24.0 |
| `github.com/fission/fission` | Go | All versions | 1.24.0 |

## How do I fix CVE-2026-49822?

Upgrade github.com/fission/fission to 1.24.0 or later.

## Is CVE-2026-49822 being exploited?

There is no known exploitation of CVE-2026-49822 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49822 and fix it if it is affected.

What it is: CVE-2026-49822 is a high-severity vulnerability in fission, published on 10 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-49822 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fission/fission (Go): affected all versions; fixed in 1.24.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.24.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.24.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-49822/ (Markdown: https://insights.sbomify.com/CVE-2026-49822/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-49822
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-49822
- OSV: https://osv.dev/vulnerability/CVE-2026-49822

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-49822/
Summaries are generated and may contain mistakes; the official description above is the record.