# CVE-2026-46614: Fission router exposes /fission-function// on its public listener, allowing invocation of any function without an HTTPTrigger > Attackers can invoke any Fission function by guessing its name, bypassing HTTPTrigger restrictions and potentially executing unauthorized code. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jun 2026 - **Updated:** 11 Jun 2026 - **Also known as:** GHSA-3g33-6vg6-27m8, GO-2026-5082 ## What is CVE-2026-46614? CVE-2026-46614 is a critical missing authorization vulnerability in fission, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, 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.23.0, the Fission router registers an internal-style route — /fission-function/ and /fission-function// — 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. This issue has been patched in version 1.23.0. Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-46614? 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.23.0 | | `github.com/fission/fission` | Go | All versions | 1.23.0 | | `github.com/fission/fission` | Go | All versions | 1.23.0 | ## How do I fix CVE-2026-46614? Upgrade github.com/fission/fission to 1.23.0 or later. ## Is CVE-2026-46614 being exploited? There is no known exploitation of CVE-2026-46614 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46614 and fix it if it is affected. What it is: CVE-2026-46614 is a critical missing authorization vulnerability in fission, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-46614 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/fission/fission (Go): affected all versions; fixed in 1.23.0 - github.com/fission/fission (Go): affected all versions; fixed in 1.23.0 - github.com/fission/fission (Go): affected all versions; fixed in 1.23.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-46614/ (Markdown: https://insights.sbomify.com/CVE-2026-46614/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46614 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46614 - OSV: https://osv.dev/vulnerability/CVE-2026-46614 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46614/ Summaries are generated and may contain mistakes; the official description above is the record.