CVE-2026-50570

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.5
EG Score
8.5(medium)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 10, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Patch available. Sources: github_pr, github_release, github.
github Patch Available

Incomplete capability denylist in Fission Environment/Function PodSpec validation allows tenant-added CAP_SYS_TIME and cross-tenant node wall-clock corruption · Advisory · fission/fission · GitHub

https://github.com/fission/fission/security/advisories/GHSA-qf5v-m7p4-95rp
github_release Patch Available

v1.25.0

Patch available: fission/fission v1.25.0

https://github.com/fission/fission/releases/tag/v1.25.0
github_pr

fix(podspec): allowlist tenant caps + force drop:[ALL] (GHSA-qf5v)

Fix merged in fission/fission PR #3465 on 2026-06-04 — awaiting tagged release

https://github.com/fission/fission/pull/3465

Vendor Advisories for CVE-2026-50570(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/fission/fission—1.25.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-08-31 00:11 UTCEG score recompute
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:49 UTCEPSS rescore
  8. 2026-08-25 00:20 UTCEG score recompute
  9. 2026-08-23 10:47 UTCEG score recompute
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 09:58 UTCEG score recompute
  13. 2026-08-20 22:55 UTCEPSS rescore
  14. 2026-08-20 08:52 UTCEG score recompute
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-19 14:56 UTCEG score recompute
  17. 2026-08-18 13:48 UTCEPSS rescore
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 23:59 UTCEG score recompute
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 11:58 UTCEG score recompute
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 10:51 UTCEG score recompute
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-13 22:16 UTCEG score recompute
Show 75 more
  1. 2026-08-13 22:00 UTCEPSS rescore
  2. 2026-08-12 20:23 UTCEG score recompute
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 20:18 UTCEG score recompute
  5. 2026-08-11 08:17 UTCEG score recompute
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-09 20:13 UTCEG score recompute
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 20:11 UTCEG score recompute
  10. 2026-08-08 16:37 UTCEPSS rescore
  11. 2026-08-07 20:09 UTCEG score recompute
  12. 2026-08-06 20:05 UTCEG score recompute
  13. 2026-08-06 13:47 UTCEPSS rescore
  14. 2026-08-05 20:01 UTCEG score recompute
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-04 15:54 UTCEG score recompute
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:39 UTCEPSS rescore
  19. 2026-08-03 14:50 UTCEG score recompute
  20. 2026-08-03 10:36 UTCEPSS rescore
  21. 2026-08-01 09:39 UTCEG score recompute
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-31 00:42 UTCEG score recompute
  24. 2026-07-30 16:28 UTCEPSS rescore
  25. 2026-07-30 09:47 UTCEG score recompute
  26. 2026-07-30 01:30 UTCEPSS rescore
  27. 2026-07-29 04:55 UTCEG score recompute
  28. 2026-07-28 15:37 UTCEPSS rescore
  29. 2026-07-28 02:18 UTCEG score recompute
  30. 2026-07-26 20:58 UTCEG score recompute
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-24 14:18 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 03:18 UTCEG score recompute
  36. 2026-07-22 14:08 UTCEPSS rescore
  37. 2026-07-21 15:25 UTCEPSS rescore
  38. 2026-07-20 17:08 UTCEPSS rescore
  39. 2026-07-19 14:31 UTCEPSS rescore
  40. 2026-07-19 14:31 UTCEPSS rescore
  41. 2026-07-19 02:29 UTCEPSS rescore
  42. 2026-07-18 10:04 UTCEPSS rescore
  43. 2026-07-16 17:03 UTCEPSS rescore
  44. 2026-07-15 16:57 UTCEPSS rescore
  45. 2026-07-15 16:57 UTCEPSS rescore
  46. 2026-07-15 02:00 UTCEPSS rescore
  47. 2026-07-15 02:00 UTCEPSS rescore
  48. 2026-07-13 22:31 UTCEPSS rescore
  49. 2026-07-13 06:13 UTCEPSS rescore
  50. 2026-07-13 06:13 UTCEPSS rescore
  51. 2026-07-12 05:46 UTCEPSS rescore
  52. 2026-07-11 08:27 UTCEPSS rescore
  53. 2026-07-11 08:27 UTCEPSS rescore
  54. 2026-07-09 19:10 UTCEPSS rescore
  55. 2026-07-09 19:10 UTCEPSS rescore
  56. 2026-07-08 15:16 UTCEPSS rescore
  57. 2026-07-08 15:16 UTCEPSS rescore
  58. 2026-07-07 13:46 UTCEPSS rescore
  59. 2026-07-07 13:46 UTCEPSS rescore
  60. 2026-07-06 16:27 UTCEPSS rescore
  61. 2026-07-06 02:23 UTCEPSS rescore
  62. 2026-07-05 02:30 UTCEPSS rescore
  63. 2026-07-01 15:07 UTCEPSS rescore
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-29 14:06 UTCEPSS rescore
  66. 2026-06-29 14:06 UTCEPSS rescore
  67. 2026-06-28 14:07 UTCEPSS rescore
  68. 2026-06-28 04:56 UTCEPSS rescore
  69. 2026-06-28 04:56 UTCEPSS rescore
  70. 2026-06-27 03:08 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-24 14:05 UTCEPSS rescore
  73. 2026-06-23 21:33 UTCEPSS rescore
  74. 2026-06-23 21:33 UTCEPSS rescore
  75. 2026-06-22 14:25 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50570?
CVE-2026-50570 is a high vulnerability published on June 10, 2026. 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 /…
When was CVE-2026-50570 disclosed?
CVE-2026-50570 was first published in the National Vulnerability Database on June 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50570 actively exploited?
CVE-2026-50570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.6% of all scored CVEs.
What is the CVSS score of CVE-2026-50570?
CVE-2026-50570 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-50570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50570, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50570

Explore →

Is Your Infrastructure Affected by CVE-2026-50570?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs