CVE-2026-32613

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 90% 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, nvd
9.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.9Exploit: NoneExposed: 0

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

Spinnaker is an open source, multi-cloud continuous delivery platform. Echo like some other services, uses SPeL (Spring Expression Language) to process information - specifically around expected artifacts. In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, unlike orca, it was NOT restricting that context to a set of trusted classes, but allowing FULL JVM access. This enabled a user to use arbitrary java classes which allow deep access to the system. This enabled the ability to invoke commands, access files, etc. Versions 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2 contain a patch. As a workaround, disable echo entirely.

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

Published

April 20, 2026

Last Modified

April 23, 2026

Advisory Details (5)

Auto-updated Jul 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
generic🟡 PoC Available

Critical Spinnaker Vulns Allow RCE And Production Compromise - ZeroPath Blog | ZeroPath

https://zeropath.com/blog/spinnaker-rce-production-compromise
github Patch Available

RCE via expression parsing due to unrestricted context handling · Advisory · spinnaker/spinnaker · GitHub

https://github.com/spinnaker/spinnaker/security/advisories/GHSA-69rw-45wj-g4v6
github_release Patch Available

Spinnaker 2026.0.1

Patch available: spinnaker/spinnaker spinnaker-release-2026.0.1

https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2026.0.1
github_release Patch Available

Spinnaker 2025.4.2

Patch available: spinnaker/spinnaker spinnaker-release-2025.4.2

https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.4.2
github_release Patch Available

Spinnaker 2025.3.2

Patch available: spinnaker/spinnaker spinnaker-release-2025.3.2

https://github.com/spinnaker/spinnaker/releases/tag/spinnaker-release-2025.3.2

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
io.spinnaker.echo:echo-pipelinetriggers2.32.1 ... main-99 (362 versions)2025.3.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32613?
CVE-2026-32613 is a critical vulnerability published on April 20, 2026. Spinnaker is an open source, multi-cloud continuous delivery platform. Echo like some other services, uses SPeL (Spring Expression Language) to process information - specifically around expected artifacts. In versions prior to 2026.1.0, 2026.0.1, 2025.4.2, and 2025.3.2, unlike orca, it was NOT…
When was CVE-2026-32613 disclosed?
CVE-2026-32613 was first published in the National Vulnerability Database on April 20, 2026, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32613 actively exploited?
CVE-2026-32613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32613?
CVE-2026-32613 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-32613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32613, 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-32613

Explore →

Is Your Infrastructure Affected by CVE-2026-32613?

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

Start Free Scan →Browse All CVEs