CVE-2026-50569: Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks
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).
Published Jul 28, 2026
Affected packages
github.com/fission/fission
- Ecosystem
- Go
- Affected
- <= 1.24.0
- Fixed in
- 1.25.0
- Check
go list -m github.com/fission/fission
Advisory details
From the GitHub Advisory Database (CC BY 4.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.
A tenant with HTTPTrigger create permission could therefore create triggers whose RelativeURL or Prefix:
- was empty (with both fields unset, the trigger has no URL),
- did not start with
/, - was exactly
/(claiming the entire router root), - contained
..traversal segments (e.g./api/../admin), - collided with router-owned routes:
/router-healthz,/readyz,/_version,/auth/login, - collided with the router-internal function prefix
/fission-function/<ns>/<name>.
Affected
- Project:
github.com/fission/fission - Versions: all versions through v1.24.0
- Audited commit:
647c141 - Component:
pkg/apis/core/v1/validation.go:HTTPTriggerSpec.Validate(and the missing CEL onHTTPTriggerSpec) - Configuration: default
Fix section (paste into the Fix / Patches field)
Fixed in v1.25.0 by:
- PR #3464 (commit `0deed6bf`) — enforce the path-safety invariants at both admission layers so the API
server's CEL evaluation and the Go-side HTTPTriggerSpec.Validate() agree:
- Three
+kubebuilder:validation:XValidationrules onHTTPTriggerSpec(the API server's CEL admission gate, regenerated intocrds/v1/fission.io_httptriggers.yaml): - at least one of
relativeurlorprefixmust be non-empty; relativeurl, when set, must start with/, must not be/, must contain no..segment, must not be in the reserved exact-path set, and must not start with/fission-function/;prefix, when set, the same rules guarded byhas(self.prefix).validateTriggerPathhelper inpkg/apis/core/v1/validation.go, invoked fromHTTPTriggerSpec.Validate(), mirrors the CEL rules so the CLI's early rejection and the router reconciler's status-Condition path match what the API
server admits.
Regression coverage: a new TestHTTPTriggerSpecValidate_Path table in pkg/apis/core/v1/validation_validators_test.go exercises every PoC case from the advisory plus literal ..-prefixed-segment positives that must remain allowed.
Credited to 0xshdax, sanketsudake.
References
- https://github.com/fission/fission/security/advisories/GHSA-vchh-r53j-8mpw
- https://nvd.nist.gov/vuln/detail/CVE-2026-50569
- https://github.com/fission/fission/pull/3464
- https://github.com/fission/fission/commit/0deed6bf3f26bc0f10e9130cd0d479b0b9f5f609
- https://github.com/fission/fission/releases/tag/v1.25.0
- https://github.com/advisories/GHSA-vchh-r53j-8mpw
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-50567
Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory
high7.7Jul 28, 2026CVE-2026-50568
Fission: SanitizeFilePath lexical HasPrefix bypass permits sibling-directory escape
low3.6Jul 28, 2026CVE-2026-50570
Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption
high8.5Jul 28, 2026CVE-2026-49821
Fission: Cross-namespace Environment reference in Package allows build-time command execution and SA token exfiltration
high7.7Jun 30, 2026CVE-2026-49822
Fission: Cross-namespace event leakage via KubernetesWatchTrigger allows persistent tenant surveillance
high7.7Jun 30, 2026CVE-2026-49823
Fission: Cross-namespace Package read via unvalidated PackageRef in Function admission webhook
high7.7Jun 30, 2026
