# CVE-2026-50570: Fission: Incomplete capability denylist in Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption

> A tenant can bypass capability restrictions to gain CAP_SYS_TIME, allowing them to alter the node's system clock and potentially disrupt other tenants.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-qf5v-m7p4-95rp, GO-2026-6129

## What is CVE-2026-50570?

CVE-2026-50570 is a high-severity vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, 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.25.0, Fission added PodSpec safety validation for tenant-facing Environment and Function CRDs (ValidatePodSpecSafety / ValidateContainerSafety admission webhook + sanitizeContainerSecurityContext executor merge layer), but the capability check was implemented as a fixed denylist of six Linux capabilities (SYS_ADMIN, NET_ADMIN, SYS_PTRACE, SYS_MODULE, DAC_READ_SEARCH, DAC_OVERRIDE). The denylist omitted CAP_SYS_TIME, among others. As a result, a tenant who could create a Function or Environment CRD could request securityContext.capabilities.add: ["SYS_TIME"], pass Fission's admission validation and merge-layer sanitization, and run attacker-controlled code with CAP_SYS_TIME in the resulting function or runtime container. This issue has been patched in version 1.25.0.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-50570?

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.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |
| `github.com/fission/fission` | Go | All versions | 1.25.0 |

## How do I fix CVE-2026-50570?

Upgrade github.com/fission/fission to 1.25.0 or later.

## Is CVE-2026-50570 being exploited?

There is no known exploitation of CVE-2026-50570 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50570 and fix it if it is affected.

What it is: CVE-2026-50570 is a high-severity vulnerability in fission, published on 10 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50570 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.0
- github.com/fission/fission (Go): affected all versions; fixed in 1.25.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-50570/ (Markdown: https://insights.sbomify.com/CVE-2026-50570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50570
- OSV: https://osv.dev/vulnerability/CVE-2026-50570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50570/
Summaries are generated and may contain mistakes; the official description above is the record.