dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-50564

CRITICAL · 9.9 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 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.24.0, Fission's Environment CRD exposes spec.runtime.podSpec and spec.builder.podSpec, which are merged into the Kubernetes pod specs for runtime and builder pods. The merge logic propagated hostNetwork, hostPID, hostIPC, container privileged, and serviceAccountName from the user-supplied podspec with no filtering, and Environment.Validate performed no security-relevant checks on these fields. This issue has been patched in version 1.24.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 Environment CRD allowed user-supplied podSpec fields to be merged into runtime and builder pods without filtering dangerous settings including hostNetwork, hostPID, hostIPC, privileged containers, and serviceAccountName, enabling potential container escape and privilege escalation.

MitigationUpgrade to Fission version 1.24.0 or later which patches the unsafe podSpec merge logic by filtering security-relevant fields in Environment.Validate.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Check installed Fission version
    Run 'fission version' or check the fission-core deployment: 'kubectl get deployment -n fission-function -o jsonpath="{.items[*].spec.template.spec.containers[0].image}"'. Compare the version to 1.24.0.
    Affected if The installed version is earlier than 1.24.0 (the patched version).
  2. List Fission Environment CRDs in the cluster
    Run 'kubectl get environments -A' to see all Environment custom resources across namespaces.
    Affected if Any Environment resources exist in the cluster.
  3. Inspect Environment CRDs for dangerous podSpec fields
    For each Environment, run 'kubectl get environment <name> -n <namespace> -o yaml' and examine the spec.runtime.podSpec and spec.builder.podSpec fields. Look specifically for: hostNetwork: true, hostPID: true, hostIPC: true, privileged: true, or any serviceAccountName setting.
    Affected if Any Environment resource contains podSpec overrides with hostNetwork, hostPID, hostIPC, privileged, or a custom serviceAccountName.
  4. Check for existing runtime or builder pods with elevated privileges
    Run 'kubectl get pods -A -o jsonpath="{.items[?(@.spec.hostNetwork || @.spec.hostPID || @.spec.hostIPC || @.spec.containers[0].securityContext.privileged)].metadata.name}"' to find pods created from Fission environments that use these dangerous settings.
    Affected if Any Fission-created pods are running with hostNetwork, hostPID, hostIPC, or privileged mode enabled.

You are affected if Fission version is below 1.24.0 AND any Environment CRDs exist with user-controlled podSpec fields that include hostNetwork, hostPID, hostIPC, privileged containers, or custom serviceAccountName settings.

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 version 1.24.0 or later which patches the unsafe podSpec merge logic by filtering security-relevant fields in Environment.Validate.

Recommended fix High confidence

1.24.0

  1. 1. Identify current Fission installation method (Helm, YAML manifests, or operator)
  2. 2. Check current Fission version: kubectl get fissionversion -o wide or helm list
  3. 3. Create a backup of current Fission custom resources: kubectl get environments -o yaml > fission-environments-backup.yaml
  4. 4. If using Helm, upgrade to version 1.24.0: helm upgrade fission fission-charts/fission-all --version 1.24.0
  5. 5. If using YAML manifests, apply the 1.24.0 release manifests from the Fission GitHub releases page
  6. 6. Verify the upgrade completed successfully: kubectl get pods -n fission-function and ensure all pods are Running
  7. 7. Confirm the Environment.Validate now performs security checks by creating a test Environment with privileged containers and verifying rejection
  8. 8. Review application functionality to ensure the upgrade did not break existing functions
Caveat General upgrade risk: test in non-production first; review Fission 1.24.0 release notes for any changes to API behavior

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
32.0 hours of engineering $5,640
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50564 — 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-50564 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