CVE-2026-59321

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2% (6th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-27) is not newer than that change (2026-08-31), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VMware by Broadcom) lists Spring Integration versions 7.0.0 up to and including 7.0.5, 6.5.0 up to and including 6.5.10, 6.4.0 up to and including 6.4.12 and up to and including 5.5.21 as affected. No release containing a fix is confirmed on record.

A single ScriptEngine instance is reused for every message on a script-backed channel. For JSR-223 engines that report THREADING=null (not thread-safe, e.g. the Kotlin kts engine), concurrent message processing can corrupt engine-internal state, potentially leaking one message's payload/headers bindings into another message's script evaluation or throwing spurious exceptions. Spring Integration 7.1.0 Spring Integration 7.0.0 - 7.0.5 Spring Integration 6.5.0 - 6.5.10 Spring Integration 6.4.0 - 6.4.12 Spring Integration 5.5.21 and earlier

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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 (value × EchelonGraph’s weight)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.2% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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

August 27, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No fix on record yet.
Web page

Shared JSR-223 ScriptEngine evaluated concurrently without THREADING check

https://spring.io/security/cve-2026-59321

Vendor Advisories for CVE-2026-59321(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 73× 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 125 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 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-59321?
CVE-2026-59321 is a medium-severity vulnerability; its CVE record was published on August 27, 2026. A single ScriptEngine instance is reused for every message on a script-backed channel. For JSR-223 engines that report THREADING=null (not thread-safe, e.g. the Kotlin kts engine), concurrent message processing can corrupt engine-internal state, potentially leaking one message's payload/headers…
When was the CVE record for CVE-2026-59321 published?
The CVE record for CVE-2026-59321 was published on August 27, 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 August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-59321 actively exploited?
CVE-2026-59321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-59321?
CVE-2026-59321 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-59321?
No fix for CVE-2026-59321 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VMware by Broadcom) lists Spring Integration versions 7.0.0 up to and including 7.0.5, 6.5.0 up to and including 6.5.10, 6.4.0 up to and including 6.4.12 and up to and including 5.5.21 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-59321 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-59321?

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