CVE-2026-46617

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% 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.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.7Exploit: 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.23.0, Fission runtime pods were created with ServiceAccountName: fission-fetcher, and the fission-fetcher ServiceAccount was granted namespace-wide get on secrets and configmaps (it needs that to load function code, env vars, and config). The runtime pod's automounted token was reachable from inside the user's function container at /var/run/secrets/kubernetes.io/serviceaccount/token, so user-supplied function code inherited the same Kubernetes API privileges and could read any secret or configmap in the function's namespace — far beyond the Function.spec.secrets allowlist that the function specification suggests. This issue has been patched in version 1.23.0.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
44
EG Risk 44/100

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
Severity87% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

Published

May 21, 2026

Last Modified

June 10, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Patch available. Sources: github_pr, github_release, github.
githubMentions a patch (unverified)

Fission runtime pods automount the fission-fetcher service-account token into the user function container, granting function code namespace-wide secret / configmap read · Advisory · fission/fission · GitHub

https://github.com/fission/fission/security/advisories/GHSA-85g2-pmrx-r49q
github_release Patch Available

v1.23.0

Patch available: fission/fission v1.23.0

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

Drop fission-fetcher SA token from function user containers

Fix merged in fission/fission PR #3366 on 2026-05-08 — awaiting tagged release

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

Vendor Advisories for CVE-2026-46617(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.23.0: fixed in 1.23.0
—

Weakness Classification(3)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46617?
CVE-2026-46617 is a high vulnerability published on May 21, 2026. Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and applications on Kubernetes. Prior to version 1.23.0, Fission runtime pods were created with ServiceAccountName: fission-fetcher, and the fission-fetcher ServiceAccount was granted…
When was CVE-2026-46617 disclosed?
CVE-2026-46617 was first published on May 21, 2026, with the most recent update 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-46617 actively exploited?
CVE-2026-46617 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46617?
CVE-2026-46617 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46617?
A fix for CVE-2026-46617 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46617 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-46617

Explore →

Is Your Infrastructure Affected by CVE-2026-46617?

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

Book a Demo →Browse All CVEs