CVE-2026-59321

Shared JSR-223 ScriptEngine evaluated concurrently without THREADING check

Published Aug 27, 2026 CVSS 3.1 · 4.2 Medium EPSS < 1% KEV · Not listed
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

Analysis

AI-generated

Technical impact

A single ScriptEngine instance is reused for every message in a script‑backed channel. For JSR‑223 engines that report THREADING=null, such as the Kotlin kts engine, concurrent message processing can corrupt the engine’s internal state. This corruption may cause one message’s payload and headers bindings to appear in another message’s script evaluation or trigger spurious exceptions, exposing sensitive information between otherwise unrelated messages.

Affected Systems

Spring Integration library versions 7.1.0, 7.0.0–7.0.5, 6.5.0–6.5.10, 6.4.0–6.4.12, and 5.5.21 or earlier by the Spring vendor.

Risk and Exploitability

The CVSS score of 4.2 indicates moderate severity, and the EPSS score is < 1%, indicating a low likelihood of exploitation, but the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector requires an actor to send messages that traverse the affected script channel, which may be possible through external interfaces or internal application logic. The potential for data leakage or service disruption warrants attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the newest Spring Integration release that resolves this issue (any version newer than 7.1.0, 7.0.5, 6.5.10, 6.4.12, or 5.5.21).
  • If an upgrade cannot be performed immediately, configure the script channel to use a thread‑safe ScriptEngine instance, or instantiate a new engine for each message to avoid shared state.
  • Limit or monitor message sources that reach the vulnerable channel and inspect logs for unexpected script evaluation errors or data leakage indicators.

Generated by OpenCVE AI on August 29, 2026 at 02:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Integration
CPEs cpe:2.3:a:vmware:spring_integration:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Integration
Type Values Removed Values Added
Weaknesses CWE-667
Type Values Removed Values Added
Weaknesses CWE-362
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Integration
Vendors & Products Spring
Spring spring Integration
Type Values Removed Values Added
Weaknesses CWE-667
Type Values Removed Values Added
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
Title Shared JSR-223 ScriptEngine evaluated concurrently without THREADING check
References
Metrics cvssV3_1

{'score': 4.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 10:46 PM
Reserved
Jul 4, 2026, 6:14 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Aug 31, 2026, 5:27 PM