CVE-2026-50570

HIGHPre-NVD 8.58.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
8.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity85% × 45%
Impact severity (EG Severity): CVSS 8.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.5): severity, escalated by confirmed exploitation. This CVE's 8.5 is its impact severity (EG Severity), not escalated.

EG Severity
8.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

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 advisoryMentions a patch (unverified)

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 pull request

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 rangeFix by version rangeDependents
github.com/fission/fission—
  • every version up to 1.25.0: fixed in 1.25.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 167 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 67 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-50570?
CVE-2026-50570 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-50570 published?
The CVE record for CVE-2026-50570 was published on June 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 10, 2026; the record at its source may have been updated since.
Is CVE-2026-50570 actively exploited?
CVE-2026-50570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50570?
CVE-2026-50570 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-50570?
A fix for CVE-2026-50570 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50570 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs