CVE-2026-59321

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

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

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.4(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 27, 2026

Last Modified

August 31, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

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 / 66× 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.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 08:19 UTCEG score recompute
  3. 2026-09-20 08:19 UTCGHSA enrichment
  4. 2026-09-19 06:31 UTCEG score recompute
  5. 2026-09-19 06:31 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 05:56 UTCGHSA enrichment
  8. 2026-09-17 05:19 UTCEG score recompute
  9. 2026-09-17 05:19 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 04:43 UTCGHSA enrichment
  12. 2026-09-15 04:08 UTCEG score recompute
  13. 2026-09-15 04:08 UTCGHSA enrichment
  14. 2026-09-15 03:11 UTCEPSS rescore
  15. 2026-09-14 03:33 UTCEG score recompute
  16. 2026-09-14 03:33 UTCGHSA enrichment
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-13 02:59 UTCEG score recompute
  19. 2026-09-13 02:59 UTCGHSA enrichment
  20. 2026-09-12 02:24 UTCEG score recompute
  21. 2026-09-12 02:24 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 01:49 UTCEG score recompute
  24. 2026-09-11 01:49 UTCGHSA enrichment
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 41 more
  1. 2026-09-10 01:14 UTCGHSA enrichment
  2. 2026-09-09 00:39 UTCEG score recompute
  3. 2026-09-09 00:39 UTCGHSA enrichment
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 23:29 UTCEG score recompute
  6. 2026-09-07 23:29 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 22:54 UTCEG score recompute
  9. 2026-09-06 22:54 UTCGHSA enrichment
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 22:20 UTCEG score recompute
  12. 2026-09-05 22:20 UTCGHSA enrichment
  13. 2026-09-04 21:43 UTCEG score recompute
  14. 2026-09-04 21:43 UTCGHSA enrichment
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-03 21:03 UTCGHSA enrichment
  17. 2026-09-02 20:28 UTCEG score recompute
  18. 2026-09-02 20:28 UTCGHSA enrichment
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 18:16 UTCEG score recompute
  21. 2026-09-01 18:16 UTCGHSA enrichment
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 17:41 UTCEG score recompute▲ 1.20
  25. 2026-08-31 17:41 UTCGHSA enrichment
  26. 2026-08-31 17:40 UTCNVD updateCVSS v3 → 5.4
  27. 2026-08-31 00:35 UTCEG score recompute
  28. 2026-08-31 00:35 UTCGHSA enrichment
  29. 2026-08-30 19:17 UTCEPSS rescore
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-30 00:00 UTCGHSA enrichment
  32. 2026-08-28 23:26 UTCEG score recompute
  33. 2026-08-28 23:25 UTCGHSA enrichment
  34. 2026-08-28 22:50 UTCEG score recompute
  35. 2026-08-28 22:49 UTCGHSA enrichment
  36. 2026-08-28 21:42 UTCEPSS rescore
  37. 2026-08-28 18:59 UTCEG score recompute
  38. 2026-08-28 18:59 UTCGHSA enrichment
  39. 2026-08-27 20:26 UTCEG score recompute
  40. 2026-08-27 20:16 UTCEG score recompute
  41. 2026-08-27 20:13 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59321?
CVE-2026-59321 is a medium vulnerability 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 CVE-2026-59321 disclosed?
CVE-2026-59321 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59321 actively exploited?
CVE-2026-59321 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59321, 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-59321

Explore →

Is Your Infrastructure Affected by CVE-2026-59321?

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

Start Free Scan →Browse All CVEs