CVEvulnerability
CVE-2026-59321
5.4 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-08-27
- Last modified
- 2026-08-31
- Assigner
- [email protected]
- CVSS 3.1 ([email protected])
- 4.2 MEDIUM — CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- CVSS 3.1 ([email protected])
- 5.4 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Weaknesses
- CWE-362
Description
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 configurations
• vmware spring integration (<= 5.5.21)
• vmware spring integration (>= 6.4.0 <= 6.4.12)
• vmware spring integration (>= 6.5.0 <= 6.5.10)
• vmware spring integration (>= 7.0.0 < 7.0.5.1)
• vmware spring integration (>= 7.1.0 < 7.1.0.1)
Related
Weakness · CWE (1)
- CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization weakness
References
- https://spring.io/security/cve-2026-59321 Vendor Advisory