# CVE-2026-50569: Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks

> Attackers can bypass URL validation checks in Fission HTTPTriggers by using kubectl or direct API calls instead of the CLI, potentially violating security policies.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-vchh-r53j-8mpw, GO-2026-6131

## What is CVE-2026-50569?

CVE-2026-50569 is a medium-severity missing authorization vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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.25.0, HTTPTriggerSpec.Validate() validated Methods, FunctionReference, Host, IngressConfig, and CorsConfig, but silently skipped RelativeURL and Prefix. Those two fields were validated at the CLI level only (pkg/fission-cli/cmd/httptrigger/create.go:83). The post-CRD-modernization webhook for HTTPTrigger was retired in favor of API-server CEL — and CEL had no rules on those fields either — so an HTTPTrigger created via kubectl apply or a direct Kubernetes REST API call bypassed every URL-level check. This issue has been patched in version 1.25.0.

Weakness: CWE-20 (Improper Input Validation)

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

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.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |

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

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

## Is CVE-2026-50569 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50569 is a medium-severity missing authorization vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50569 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.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-50569/ (Markdown: https://insights.sbomify.com/CVE-2026-50569/index.md)
```

## Sources

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

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