CVE-2026-50563
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 · uneditedFission 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 Container Executor path lets a tenant supply Function.spec.podspec directly; the executor merges it into the executor-built podspec and creates a Deployment whose pods run the user's container image. 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 confidenceFission's Container Executor allows tenants to directly supply Function.spec.podspec which gets merged into the executor-built podspec, creating a Deployment that runs arbitrary user-provided container images without proper validation - enabling potential privilege escalation or execution of untrusted/malicious containers.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Fission installationRun 'fission version' or check the installed Fission Helm chart version, or look at the deployment namespace for Fission pods and check their image tagsAffected if The installed version is earlier than 1.24.0 (this vulnerability is patched in 1.24.0 and later)
-
Determine if Container Executor is activeCheck if the Fission environment is using 'container' as the executor type. Run 'fission function list' and inspect the executor type, or query the Kubernetes custom resources for Function definitionsAffected if Functions are using the container executor and custom podspecs can be attached to function definitions
-
Review existing function definitions for podspec usageQuery the Function custom resources: 'kubectl get functions -A -o yaml' and examine whether any Function resources contain a 'podspec' field in their specAffected if Any Function resource contains a user-supplied 'podspec' field that could inject arbitrary container images
-
Check for unauthorized container images in the clusterReview recent pod creations in namespaces where Fission functions run. Check for pods with container images from untrusted registries or unexpected image namesAffected if Pods exist with container images that were not explicitly authorized or expected in the function deployment pipeline
You are affected if Fission version is below 1.24.0 AND the Container Executor is in use with functions that accept custom podspec definitions.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Fission to version 1.24.0 or later which contains the patch for this vulnerability.
Fission version 1.24.0
- Upgrade Fission to version 1.24.0 or later
- Verify the upgrade completed successfully by checking the Fission deployment status
- Confirm that Function.spec.podspec is no longer directly merged into executor-built podspecs (this is an internal fix)
- Test existing functions to ensure they work as expected post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50563 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50563 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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