CVE-2026-59321: Shared JSR-223 ScriptEngine evaluated concurrently without THREADING check
Spring · Spring Integration
Affected: Spring Integration · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 7% of scored CVEs
DescriptionCVE.org
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
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Spring · Spring Integration7.1.0; from 7.0.0 up to and including 7.0.5; from 6.5.0 up to and including 6.5.10; from 6.4.0 up to and including 6.4.12; up to and including 5.5.21
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Race Condition · Race Conditions
- Vendor
- Spring
- Published
- August 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-59321 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.