dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-46614

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/<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. This issue has been patched in version 1.23.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Fission router registers internal-style routes (/fission-function/<name> and /fission-function/<ns>/<name>) for every Function object regardless of HTTPTrigger existence, mounting them on the same listener (svc/router:8888) as user-defined triggers. This allows any network-accessible caller to invoke any function by guessing its name and namespace, completely bypassing HTTPTrigger-defined host/path/method restrictions.

MitigationUpgrade to Fission 1.23.0 or later which patches this vulnerability; if immediate upgrade is not feasible, implement network policies or firewall rules restricting access to the router service on port 8888.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Fission installation and version
    Run 'kubectl get pods -n fission-function' to list Fission components, then check the router pod image version with 'kubectl get pod -n fission-function -l executor=fission-router -o jsonpath="{.items[*].spec.containers[*].image}"'
    Affected if Fission is installed and the version is earlier than 1.23.0 (the version number in the image tag is less than 1.23.0)
  2. Confirm router service exists
    Run 'kubectl get svc router -n fission-function' to verify the router service on port 8888 exists
    Affected if The router service (svc/router) exists in the fission-function namespace on port 8888
  3. Identify function resources
    Run 'kubectl get functions -A' to list all Function objects in the cluster
    Affected if Any Function resources exist in the cluster (the vulnerability affects any function, even those without HTTPTriggers)
  4. Check if router is externally accessible
    Run 'kubectl get svc router -n fission-function -o jsonpath="{.spec.type}"' to check service type; if ClusterIP with no network policy, it may still be accessible within the cluster network
    Affected if The router service is accessible beyond the cluster's internal network (type LoadBalancer or NodePort) or has no NetworkPolicy restricting access
  5. Verify HTTPTrigger bindings exist for functions
    Run 'kubectl get httptriggers -A' and compare to 'kubectl get functions -A'; check if functions are referenced by name in HTTPTriggers
    Affected if There are functions that do NOT have corresponding HTTPTriggers, as these are the primary targets that should be protected but are exposed via the internal routes

Your environment is affected if Fission version is earlier than 1.23.0, the router service on port 8888 is network-accessible, and functions exist in the cluster (especially those without HTTPTrigger definitions).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Fission 1.23.0 or later which patches this vulnerability; if immediate upgrade is not feasible, implement network policies or firewall rules restricting access to the router service on port 8888.

Recommended fix High confidence

1.23.0

  1. Upgrade Fission to version 1.23.0 or later to remediate this vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46614 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data