CVE-2026-50563

CRITICALPre-NVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under the CNA's CVSS (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: cna:github_m, epss
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.9Exploit: NoneExposed: 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.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.

CVSS v3
9.9
EG Score
9.9(medium)
EPSS
19.2%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 12, 2026

Advisory Details (3)

Auto-updated Jul 4, 2026
Patch available. Sources: github, github_pr, github_release.
github_release Patch Available

v1.24.0

Patch available: fission/fission v1.24.0 (pre-release)

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

Reject dangerous PodSpec fields in Environment + Function (GHSA-gx55,…

Fix merged in fission/fission PR #3391 on 2026-05-23 — awaiting tagged release

https://github.com/fission/fission/pull/3391
github Patch Available

Fission Container Executor Function PodSpec Injection Leading to Node Escape · Advisory · fission/fission · GitHub

https://github.com/fission/fission/security/advisories/GHSA-v455-mv2v-5g92

Vendor Advisories for CVE-2026-50563(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 183× 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 183 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-50563?
CVE-2026-50563 is a critical 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.24.0, Fission's Container Executor path lets a tenant supply Function.spec.podspec directly; the executor merges it into the…
When was CVE-2026-50563 disclosed?
CVE-2026-50563 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50563 actively exploited?
CVE-2026-50563 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50563?
CVE-2026-50563 has a CVSS v4.0 base score of 9.9 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-50563?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50563, 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

Explore the affected products and dependency analysis for CVE-2026-50563

Explore →

Is Your Infrastructure Affected by CVE-2026-50563?

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