CVE-2026-50569: Fission · HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks
Affects github.com/fission/fissionSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.25.0 when convenient.
Data as of 27 Oct 2026, 05:11 UTC
- 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.25.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade github.com/fission/fission to 1.25.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gogithub.com/fission/fission | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Fission version 1.25.0. Users should upgrade to version 1.25.0 or later to ensure that RelativeURL and Prefix fields are properly validated at both the API server and CLI levels. Prior to upgrading, avoid creating HTTPTriggers with RelativeURL or Prefix fields via kubectl apply or direct API calls. The patch enforces path safety invariants and prevents unsafe URL configurations.
Description
A validation bypass vulnerability exists in the HTTPTrigger resource of the Fission project (github.com/fission/fission) through version 1.24.0. The fields RelativeURL and Prefix were only validated at the CLI level, not at the API server admission level, allowing creation of HTTPTriggers with unsafe or conflicting URL paths via kubectl apply or direct API calls. This could lead to triggers with empty URLs, paths not starting with '/', paths containing directory traversal segments, or collisions with reserved router paths. The issue was fixed in version 1.25.0 by enforcing consistent validation rules at both the API server and CLI layers.
References
- github.com/fission/fission/security/advisories/GHSA-vchh-r53j-8mpw (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-50569 (opens in a new tab)
- github.com/fission/fission/pull/3464 (opens in a new tab)
- github.com/fission/fission/commit/0deed6bf3f26bc0f10e9130cd0d479b0b9f5f609 (opens in a new tab)
- github.com/fission/fission (opens in a new tab)
- github.com/fission/fission/releases/tag/v1.25.0 (opens in a new tab)