CVE-2026-59273: Spring SpEL remote code execution flaw

Spring has published fixes for 50 security vulnerabilities across its Java portfolio, including a critical remote code execution flaw rated 9.8 out of 10. The most severe issue, CVE-2026-59273, affects Spring Security and was disclosed in an official advisory on 19 November 2026.
The flaw lies in ELRequestMatcher, a Spring Security component that matches web requests using Spring Expression Language, or SpEL. According to Spring's advisory, the matcher evaluates a supplied SpEL expression against an unrestricted evaluation context that grants full reflection, type references and arbitrary method invocation, rather than a context limited to its documented request-matching operations.
The danger arises from the way Spring Framework's data binding works. It automatically discovers a property editor for this matcher type by naming convention, so an application that binds external input to a bean property of this type can have that input transparently evaluated as a SpEL expression under the permissive context. An attacker who controls such input can therefore achieve remote code execution inside the application's process, without needing to log in.
The vulnerability affects Spring Security versions 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. Fixed versions are 7.1.3 and 7.0.9 for open-source users, with patched releases for the older lines available through enterprise support. Spring says no further mitigation steps are necessary once the fixed version is installed.
A second critical flaw in the same batch, CVE-2026-59367, is rated 9.4 and affects the test LDAP support in Spring Security. A further high-severity issue, CVE-2026-123886, rated 8.8, affects Spring Data Elasticsearch. The November update also covers Spring AI and several other Spring projects, with fixes including Spring Security 7.1.3 and 7.0.9, Spring Data Elasticsearch 6.1.3 and 6.0.9, and Spring AI 2.0.3. In total, the advisories span ten CVEs, two of them critical and eight high severity.
There is no confirmed exploitation in the wild so far, and no public exploit code is known for these flaws. That is reassuring, but it is not a reason to delay. Spring Security and the wider Spring portfolio sit at the heart of countless enterprise Java applications, and a remotely exploitable code execution flaw in a request-matching component is exactly the kind of issue attackers study closely once the details are public.
Development teams should check which Spring versions their applications run, upgrade to the fixed releases straight away and review any code that binds user-supplied input to request matchers or other SpEL-evaluated components. Applications that cannot be patched immediately should be reviewed for exposure of the affected matcher to untrusted input while an upgrade is arranged.
Sources: Spring.io; Security Online.