Fission router exposes /fission-function/ / on its public listener, allowing invocation of any function without an HTTPTrigger

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-46614: 0.35% estimated exploitation activity in the next 30 days; percentile 29.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The Fission router registers an internal-style route — /fission-function/<name and /fission-function/<ns/<name — for every Function object, independent of whether any HTTPTrigger exists for that function. The route was mounted on the same listener as user-defined HTTPTriggers (svc/router, port 8888), so any caller who could reach the router could invoke any function by guessing its metadata.name (and namespace), bypassing the host / path / method / method-allow-list restrictions encoded in HTTPTrigger objects. Affected component - pkg/router/httpTriggers.go:280-284 — internalRoute registration via utils.UrlForFunction(fn.Name, fn.Namespace), bound to the function handler. Impact An external caller who reaches the public router could: 1. Invoke functions that the operator intentionally did not publish through an HTTPTrigger (e.g. functions used only as Kubewatcher / Timer / MessageQueue trigger targets, internal helpers, or sample functions). 2. Bypass HTTPTrigger-level…

Published by the source

21 May 2026, 20:14 UTC

Last modified by the source

10 Jun 2026, 18:41 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3g33-6vg6-27m8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-46614

Advisory: Fission router exposes /fission-function/ / on its public listener, allowing invocation of any function without an HTTPTrigger
IDs: CVE-2026-46614, GHSA-3g33-6vg6-27m8
Record: https://patchnext.com/advisories/cve-2026-46614 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fission/fission 1.23.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fission/fission: affected <= 1.22.0; fixed in 1.23.0

## Suggested inspection (read-only)
- Go github.com/fission/fission: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fission/fission.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3g33-6vg6-27m8 (GitHub-reviewed advisory GHSA-3g33-6vg6-27m8 lists affected ranges: Go github.com/fission/fission >=0 <=1.22.0)

Commands are suggestions: review each one before running it.