Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-59321: A single ScriptEngine instance is reused for every message on a script-backed channel

16
Routine
MEDIUM 4.2UPGRADE

CVE-2026-59321 is a medium-severity flaw (CVSS 4.2) affecting spring integration. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 Integr

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score4.2 (Medium)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 93%)
CISA exploited listNo
WeaknessCWE-362
Published2026-08-27
Last modified2026-08-31
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-08-31 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring integration UPGRADE
Affected: <= 5.5.21 · >= 6.4.0 and <= 6.4.12 · >= 6.5.0 and <= 6.5.10 · >= 7.0.0 and < 7.0.5.1 · >= 7.1.0 and < 7.1.0.1
Fixed in: 7.0.5.1, 7.1.0.1
Safe to downgrade to: a release before 6.4.0
1. Check installed version
apt-cache policy spring-integration || rpm -q spring-integration || spring-integration --version
2. UPGRADE to 7.0.5.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-integration
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-integration
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.4.0 (Debian / Ubuntu)
apt-cache madison spring-integration sudo apt install spring-integration=<VERSION_BEFORE_6.4.0> sudo apt-mark hold spring-integration
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-integration sudo dnf downgrade spring-integration-<VERSION_BEFORE_6.4.0> sudo dnf versionlock add spring-integration
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59321?

spring integration: upgrade to 7.0.5.1, 7.1.0.1. Exact commands for each OS are on this page.

Is CVE-2026-59321 being exploited?

CVE-2026-59321 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59321 affect?

CVE-2026-59321 affects spring integration. Severity is medium (CVSS 4.2). 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 s

How urgent is CVE-2026-59321?

Priority 16/100. No elevated risk signals yet.

Software pages

VMware vulnerabilities · Kotlin vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.