CVE-2026-50545
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, the Environment.spec.runtime.podSpec / spec.builder.podSpec passthrough lacked validation, and MergePodSpec propagated dangerous fields into the generated pods. 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 confidenceIn Fission versions prior to 1.24.0, the Environment.spec.runtime.podSpec and spec.builder.podSpec fields were passed through to generated pods without validation. The MergePodSpec function propagated dangerous fields (such as hostPath mounts, privileged mode, additional capabilities, etc.) into the pod specs, allowing attackers to escape container isolation and gain host access.
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.
-
Check installed Fission versionRun `helm list -n fission` or `fission version` (or check the fission controller pod image tag) to determine the installed versionAffected if Version is prior to 1.24.0
-
List all Environment resources with podSpec definitionsRun `kubectl get environments -A -o jsonpath='{range .items[*]}{.metadata.namespace}{.metadata.name}{.spec.runtime}{.spec.builder}{end}'` or examine each Environment's YAML for runtime.podSpec or builder.podSpec fieldsAffected if Any Environment resource contains runtime.podSpec or builder.podSpec configuration
-
Inspect podSpec for dangerous fieldsFor each Environment with podSpec, examine the podSpec content for dangerous configurations: hostPath type volumes (hostPath in volumes), privileged: true, or capabilities.add entriesAffected if The podSpec contains hostPath volume mounts, privileged mode, or additional capabilities that could escape container isolation
-
Verify if affected environments are actively usedCheck if functions are using the affected environments by running `kubectl get functions -A` and cross-referencing with environment namesAffected if Functions are deployed using environments with dangerous podSpec configurations in a Fission version prior to 1.24.0
You are affected if Fission version is prior to 1.24.0 AND any Environment resource with runtime.podSpec or builder.podSpec contains dangerous fields such as hostPath mounts, privileged mode, or additional capabilities.
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 to receive the patched code that validates and sanitizes podSpec fields before merging them into generated pods.
1.24.0
- Identify current Fission version using 'fission version' or checking the installed Helm chart
- Review the Fission 1.24.0 release notes for any migration requirements or breaking changes
- Upgrade Fission to version 1.24.0 or later using the standard upgrade method (Helm upgrade for Helm-based installations)
- Verify the upgrade was successful by checking the Fission controller pods are running
- Confirm that Environment podSpec and builder podSpec fields are now properly validated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50545 — 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-50545 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