Skip to content
VMwareCVE-2026-59321

VMware Spring Integration: race condition

Medium4.2CVE-2026-59321 · Published Aug 27, 2026 · updated Aug 31, 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 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

VMware advisory

Affected versions

PackageAffectedFixed in
Spring Integration
Product
<= 7.1.0No fix yet
>= 7.0.0, <= 7.0.5No fix yet
>= 6.5.0, <= 6.5.10No fix yet
>= 6.4.0, <= 6.4.12No fix yet
Details and references
CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Severity from
the vendor (its own CVE record or advisory)
Weakness
CWE-362

More VMware advisories

All VMware
Advisory
VMware Spring AMQP: resource leak
Medium6.5Aug 27
VMware Spring Integration: improper input validation
Medium6.3Aug 27
VMware Spring Integration: race condition
High8.2Aug 27
VMware Spring Integration: unsafe deserialization
High8.0Aug 27
VMware Spring Integration: link following
Medium6.8Aug 27
Spring MVC applications using the functional web framework are vulnerable to...
Critical9.8Aug 27

Critical advisories by email

Wednesdays: the week’s critical and high advisories in the AI and data stack, with the fixed versions. Only in weeks that have some.

Double opt-in. Unsubscribe any time.