Skip to content
TrustList
Security advisories

Spring Security fixes a SpEL code execution flaw in a batch of 29 CVEs

Editorial

By TrustList Editorial

CVE-2026-59273 lets bound input reach an unrestricted SpEL context in ELRequestMatcher; fixes are 7.1.3 and 7.0.9 in open source, with Spring AI and Spring Data Elasticsearch also patched.

About Spring Security fixes a SpEL code execution flaw in a batch of 29 CVEs

Spring Security fixes a SpEL code execution flaw in a batch of 29 CVEs

19 November 2026: The Spring project has published a large set of security advisories across Spring Security, Spring AI, Spring Boot, Spring Framework and several data and integration modules. The most serious, CVE-2026-59273 in Spring Security, can let an attacker run code inside the application when external input is bound to a request matcher. Italy's national cybersecurity agency, which issued an alert the next day, counts 29 vulnerabilities in the set and rates their systemic impact as high. Neither Spring nor the agency reports exploitation.

Not yet independently verified. Spring's advisory index, read on 21 November 2026, marks one of the 19 November advisories as critical, while Italy's national cybersecurity agency counts 29 CVEs, five of them critical. We read four of the advisories in full; the others' fixed versions are not listed here. We will update this when it can be confirmed, and remove this note.

How CVE-2026-59273 turns input into code

ELRequestMatcher in Spring Security evaluates a SpEL expression against an unrestricted evaluation context, one that allows full reflection, type references and arbitrary method calls, instead of a context limited to request matching. Because Spring Framework's data binding finds a property editor for this type by naming convention, an application that binds external input to a bean property of the matcher type can have that input evaluated as SpEL. An attacker who controls that input can then execute code in the application's process. The advisory's CVSS vector is network, low complexity and no privileges.

Spring Security 7.1.0 to 7.1.2, 7.0.0 to 7.0.8, 6.5.0 to 6.5.12, 6.4.0 to 6.4.19, 5.8.0 to 5.8.28 and 5.7.26 and earlier are affected. The open-source fixes are 7.1.3 and 7.0.9. Fixes for 6.5.13, 6.4.20, 5.8.29 and 5.7.27, and the 7.1.2.1 and 7.0.8.1 builds, are for Enterprise Support customers only, so teams still on the 6.x line without that support have to move to 7.x.

Spring AI and Spring Data Elasticsearch

Two Spring AI advisories affect applications that handle untrusted documents or retrieval filters. CVE-2026-59338 is in TikaDocumentReader, whose default configuration turns off Apache Tika's content-size limit, so a large uploaded document can exhaust the JVM heap. CVE-2026-59339 is in the vector store filter expression parser, which has no nesting limit: a filter full of nested parentheses overflows the thread's stack, and repeated requests can tie up a worker pool. Both affect Spring AI 2.0.0 to 2.0.2, 1.1.0 to 1.1.9 and 1.0.0 to 1.0.10, and are fixed in 2.0.3 for everyone and in 1.1.10 and 1.0.11 for Enterprise Support customers.

CVE-2026-123886 in Spring Data Elasticsearch is a code execution flaw: positional placeholders in string-based @Query methods are filled with method arguments before SpEL is evaluated, so an argument carrying a SpEL expression is executed. Versions 6.1.0 to 6.1.2 and 6.0.0 to 6.0.8 are fixed in 6.1.3 and 6.0.9. Where an upgrade is not possible, Spring says to reject input containing #{ or to build such queries with CriteriaQuery or NativeQuery.

The rest of the set

The Italian alert lists affected versions up to and including Spring Boot 4.1.2, 4.0.9, 3.5.17, 3.4.18 and 2.7.35, Spring Framework 7.0.10 and 6.2.20, Spring Cloud Gateway 5.0.4, 4.3.6 and 4.2.10, Spring Cloud Config 5.0.6, Spring Integration 7.1.2, Spring LDAP 4.1.2 and Spring Web Services 5.0.3. The flaw types it names run from remote code execution and authentication bypass to file writes and deletion, denial of service and information disclosure. Each product's fixed release is named in its own advisory on Spring's security page, which is the list to check pinned versions against.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in