Spring Security · CVE-2026-59273
Spring Security EL
Patch now if…Runs code, but only if apps bind input to a matcher.
Spring rates this Spring Security bug Critical: ELRequestMatcher evaluates its expression with full SpEL, so whoever controls that expression can run code on the server. It's only reachable if an app lets outside input be bound onto a RequestMatcher property, a string conversion meant for XML bean definitions. There's no working public exploit, and free fixes exist only for Spring Security 7.0 and 7.1.
Part of the Spring Nov release roundup: see all 90 advisories →
How scary is it?
Are you affected? only if all are true
1Spring Security 7.1.2 or oldercommand
Affected: 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 older. Spring Boot 4.1.3 and 4.0.10 bring in the fixed 7.1.3 and 7.0.9.1,8,9
mvn dependency:list | grep spring-security2Outside input reaches a RequestMatcher property
The app has to bind external input to a bean property of this matcher type. Spring's data binding then turns the string into an ELRequestMatcher and evaluates it. The conversion exists so a string can be used "in a BeanDefinition", like the hasIpAddress(...) map keys of an XML-configured DelegatingAuthenticationEntryPoint, where the expression comes from your own config. Spring's advisory doesn't give a concrete vulnerable app pattern.1,2,3
What to do
1Upgrade to 7.1.3 or 7.0.9
On Spring Boot 4, upgrading Boot to 4.1.3 or 4.0.10 does this for you. The fix makes ELRequestMatcher use a restricted SpEL context that can't call arbitrary code.1,4,8,9
Latest safe versions checked 20 Nov
2On 6.x or 5.x: no free fixcommand
Spring's fixes for 6.5, 6.4, 5.8 and 5.7 (6.5.13, 6.4.20, 5.8.29, 5.7.27) are only for Enterprise support customers, and the advisory lists no workaround. Until you can move to 7.x, check that no request data, form field or external config value is bound onto a RequestMatcher property.1
grep -rn "RequestMatcher" --include=*.java --include=*.xml src/3Ignore the "PoC" repos
The one GitHub repo calling itself a proof of concept contained only a short README and no code on 20 Nov.5
This page shows you how to check. It can't tell you you're safe.
Sources (9) and changelog
- Spring: CVE-2026-59273 advisory 19 Nov
- Spring Security source: ELRequestMatcher
- Spring Security source: RequestMatcherEditor ("in a BeanDefinition")
- Spring Security: fix commit, restricted SpEL context
- GitHub: the only 'PoC' repo is a README
- CISA KEV catalog: not listed
- SecurityOnline: no confirmed exploitation
- Spring Boot 4.1.3 release: Spring Security 7.1.3
- Spring Boot 4.0.10 release: Spring Security 7.0.9
- Published.