CVE-2026-59321

Analyzed Analyzed - Analysis Complete

State Corruption in Spring Integration via Reused ScriptEngine

Publication date: 2026-08-27

Last updated on: 2026-08-31

Assigner: VMware

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-08-31

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-59321

Affected Vendors & Products

Vendor	Product	Version / Range
vmware	spring_integration	From 6.4.0 (inc) to 6.4.12 (inc)
vmware	spring_integration	From 6.5.0 (inc) to 6.5.10 (inc)
vmware	spring_integration	to 5.5.21 (inc)
vmware	spring_integration	From 7.0.0 (inc) to 7.0.5.1 (exc)
vmware	spring_integration	From 7.1.0 (inc) to 7.1.0.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-362	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

Executive Summary

This vulnerability involves a single ScriptEngine being reused for every message on a script-backed channel in Spring Integration. For JSR-223 engines that are not thread-safe (like the Kotlin kts engine), concurrent message processing can corrupt the engine's internal state. This may cause one message's data to leak into another's evaluation or trigger unexpected errors.

Detection Guidance

Detecting this vulnerability requires checking if your Spring Integration version is affected. Use commands like 'find / -name "spring-integration*.jar" 2>/dev/null' to locate JAR files and 'unzip -p <jar-file> META-INF/MANIFEST.MF | grep Implementation-Version' to check versions. Compare against affected ranges: 5.5.21 and earlier, 6.4.0-6.5.10, 7.0.0-7.0.5, or 7.1.0.

Impact Analysis

The impact includes potential information disclosure where one user's message data (payload or headers) could be exposed to another user's script evaluation. It may also cause system instability by throwing spurious exceptions during concurrent message processing.

Compliance Impact

This vulnerability could lead to data confidentiality breaches, violating GDPR's data protection principles or HIPAA's privacy rules. Unauthorized data exposure between users may result in non-compliance with these regulations.

Mitigation Strategies

Upgrade to a fixed version of Spring Integration. For Spring Integration 5.x users, upgrade to 5.5.22 or later. For 6.x users, upgrade to 6.5.11 or later. For 7.0.x users, upgrade to 7.0.6 or later. For 7.1.x users, upgrade to 7.1.1 or later. No additional mitigation steps are required beyond applying these updates.

Hi! I’m here to help you understand CVE-2026-59321. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70