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
CVE-2026-59307
Score 8.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 8.0; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.0
- EG Score
- 8.0(high)
- EG Risk
- 36(Track)EG Risk 36/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity80% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 29, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale reference
https://spring.io/security/cve-2026-59307Vendor Advisories for CVE-2026-59307(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-29 04:28 UTCEG score recompute
- 2026-08-29 04:27 UTCGHSA enrichment
- 2026-08-29 04:06 UTCEG score recompute
- 2026-08-29 04:06 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 20:42 UTCGHSA enrichment
- 2026-08-28 18:59 UTCGHSA enrichment
- 2026-08-28 08:49 UTCEG score recompute
- 2026-08-28 08:48 UTCGHSA enrichment
- 2026-08-27 20:26 UTCEG score recompute
- 2026-08-27 20:16 UTCEG score recompute
- 2026-08-27 20:13 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-10992EG 9.8EPSS p95CRITICAL
- CVE-2013-4521EG 9.8EPSS p90CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS p98CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-10934EG 9.8CRITICAL
- CVE-2016-9498EG 9.8EPSS p97CRITICAL
- CVE-2016-9483EG 9.8CRITICAL
- CVE-2015-2020EG 9.8CRITICAL
- CVE-2017-15692EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-59307?
When was CVE-2026-59307 disclosed?
Is CVE-2026-59307 actively exploited?
What is the CVSS score of CVE-2026-59307?
How do I remediate CVE-2026-59307?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59307
Is Your Infrastructure Affected by CVE-2026-59307?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.