CVE-2026-50569: Fission HTTPTrigger Admission Omits RelativeURL / Vulnerability

MODERATE
Advisory Identifier: GHSA-vchh-r53j-8mpw
CVSS 4.3
CWE-20
Published
Advisory Summary

CVE-2026-50569 is a MODERATE (CVSS 4.3) httptrigger admission omits relativeurl / vulnerability (CWE-20: Improper Input Validation) affecting Fission libraries in the Go ecosystem. The issue involves httptrigger admission omits relativeurl / prefix validation; kubectl apply bypasses cli checks. Remediation is available by upgrading affected packages to version 1.25.0.

CVE-2026-50569 at a Glance

CVE Identifier CVE-2026-50569
GHSA Identifier GHSA-vchh-r53j-8mpw
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-20: Improper Input Validation
Affected Product Fission
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 4.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-50569

To remediate this vulnerability, upgrade all affected Fission dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/fission/fission fixed: 1.25.0
Upgrade github.com/fission/fission to 1.25.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/fission/fission

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-50569, inspect your project dependencies for Fission:

inspect dependencies for github.com/fission/fission

Analyze the terminal output to locate any version of Fission in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.25.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Fission, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

`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 on `HTTPTriggerSpec`) - Configuration: default Fix section (paste into the Fix / Patches field) Fixed in [v1.25.0](https://github.com/fission/fission/releases/tag/v1.25.0) by: - [PR #3464](https://github.com/fission/fission/pull/3464) (commit [`0deed6bf`](https://github.com/fission/fission/commit/0deed6bf2af2a0c0c6094b25e1a0afad36773e3b)) — 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:XValidation` rules on `HTTPTriggerSpec` (the API server's CEL admission gate, regenerated into `crds/v1/fission.io_httptriggers.yaml`): - at least one of `relativeurl` or `prefix` must 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 by `has(self.prefix)`. - `validateTriggerPath` helper in `pkg/apis/core/v1/validation.go`, invoked from `HTTPTriggerSpec.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.

CVE-2026-50569 Affected Fission Versions

1 component(s)
Fixed Versions:
1.25.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/fission/fission
Go
< 1.25.0
1.25.0

References

Frequently Asked Questions

What is CVE-2026-50569?
CVE-2026-50569 is a security vulnerability in Fission involving HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks under CWE-20: Improper Input Validation.
Which Fission versions are affected?
Affected versions include releases prior to 1.25.0 across affected packages: github.com/fission/fission.
What version fixes CVE-2026-50569?
Upgrading to 1.25.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/fission/fission affected?
Yes, github.com/fission/fission is affected in releases prior to 1.25.0. Upgrade your dependency to 1.25.0 or later.
What is the CVSS score of CVE-2026-50569?
CVE-2026-50569 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-50569?
CVE-2026-50569 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Go dependencies for CVE-2026-50569?
Run the dependency tree command: 'inspect dependencies for github.com/fission/fission'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vchh-r53j-8mpw",
  "modified" : "2026-07-28T20:16:00Z",
  "published" : "2026-07-28T20:16:00Z",
  "aliases" : [ "CVE-2026-50569" ],
  "summary" : "Fission: HTTPTrigger admission omits RelativeURL / Prefix validation; kubectl apply bypasses CLI checks",
  "details" : "`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\n(`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\na direct Kubernetes REST API call bypassed every URL-level check.\n\nA tenant with HTTPTrigger create permission could therefore create triggers whose `RelativeURL` or `Prefix`:\n\n- was empty (with both fields unset, the trigger has no URL),\n- did not start with `/`,\n- was exactly `/` (claiming the entire router root),\n- contained `..` traversal segments (e.g. `/api/../admin`),\n- collided with router-owned routes: `/router-healthz`, `/readyz`, `/_version`, `/auth/login`,\n- collided with the router-internal function prefix `/fission-function/<ns>/<name>`.\n\n### Affected\n\n- Project: `github.com/fission/fission`\n- Versions: all versions through v1.24.0\n- Audited commit: `647c141`\n- Component: `pkg/apis/core/v1/validation.go:HTTPTriggerSpec.Validate` (and the missing CEL on `HTTPTriggerSpec`)\n- Configuration: default\n\nFix section (paste into the Fix / Patches field)\n\nFixed in [v1.25.0](https://github.com/fission/fission/releases/tag/v1.25.0) by:\n\n- [PR #3464](https://github.com/fission/fission/pull/3464) (commit [`0deed6bf`](https://github.com/fission/fission/commit/0deed6bf2af2a0c0c6094b25e1a0afad36773e3b)) — enforce the path-safety invariants at both admission layers so the API\nserver's CEL evaluation and the Go-side `HTTPTriggerSpec.Validate()` agree:\n  - Three `+kubebuilder:validation:XValidation` rules on `HTTPTriggerSpec` (the API server's CEL admission gate, regenerated into `crds/v1/fission.io_httptriggers.yaml`):\n    - at least one of `relativeurl` or `prefix` must be non-empty;\n    - `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/`;\n    - `prefix`, when set, the same rules guarded by `has(self.prefix)`.\n  - `validateTriggerPath` helper in `pkg/apis/core/v1/validation.go`, invoked from `HTTPTriggerSpec.Validate()`, mirrors the CEL rules so the CLI's early rejection and the router reconciler's status-Condition path match what the API\nserver admits.\n\nRegression 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fission/fission"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.25.0"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.24.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/security/advisories/GHSA-vchh-r53j-8mpw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-50569"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/pull/3464"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/commit/0deed6bf3f26bc0f10e9130cd0d479b0b9f5f609"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fission/fission"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fission/fission/releases/tag/v1.25.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-28T20:16:00Z",
    "nvd_published_at" : "2026-06-10T18:17:13Z"
  }
}