CVE-2026-59307

Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale reference

HIGH
8
CVSS Score
Published: August 27, 2026 at 05:58 PM UTC
Updated: August 31, 2026 at 06:26 PM UTC
2 products affected across 2 vendorsSpring IntegrationSpring Integration

Using Spring Integration by Spring?

Get instant alerts when new vulnerabilities affect Spring Integration - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

An operator who calls JdbcMessageStore.addAllowedPatterns(...) to restrict deserialization receives no protection at all when the store is a Spring-managed bean. 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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.4.0 ≤ v ≤ 6.4.126.5.0 ≤ v ≤ 6.5.107.0.0 ≤ v ≤ 7.0.57.1.07.1.0 milestone17.1.0 milestone27.1.0 milestone37.1.0 rc1
6.4.0 ≤ v ≤ 6.4.126.5.0 ≤ v ≤ 6.5.107.0.0 ≤ v ≤ 7.0.56.4.06.5.07.0.07.1.0

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

Vendor Advisory
Source: cverecord
https://spring.io/security/cve-2026-59307

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8HIGHvmware
Attack Vector
NETWORK
Complexity
HIGH
Privileges
HIGH
User Interaction
NONE
Scope
CHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-502

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card