CVE-2016-9879: Security Constraint Bypass in Spring Security
Summary
CVE-2016-9879: Security Constraint Bypass in Spring Security. Affects org.springframework.security:spring-security-core across 3 version ranges.
< 3.2.10.RELEASE
>= 4.0.0.RELEASE, < 4.1.4.RELEASE
>= 4.2.0.RELEASE, < 4.2.1.RELEASE
Fixed in 3.2.10.RELEASE, 4.1.4.RELEASE or 4.2.1.RELEASE, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Spring Security is a widely used security framework for Java applications. It provides authentication and authorization functionalities to secure web applications. However, a vulnerability has been discovered in Spring Security that allows attackers to bypass security constraints. This vulnerability arises from the mishandling of URL path parameters by Spring Security, which can result in the bypassing of security constraints. The issue affects various versions of Spring Security, including 3.2.0 - 3.2.9, 4.0.x - 4.1.3, and 4.2.0.
Vulnerability Detail
The vulnerability in Spring Security arises from the lack of consideration for URL path parameters when processing security constraints. By adding an encoded "/" as a URL path parameter to a request, an attacker can potentially bypass a security constraint. This occurs because Spring Security uses the value returned by getPathInfo(), which may or may not include path parameters depending on the Servlet container being used. Some containers, like Apache Tomcat, strip path parameters, while others may include them. This inconsistency can lead to the bypassing of security constraints.
How To Fix
Latest published version: 7.2.0-RC1 as of 23 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 3.2.10.RELEASE3.2.10.RELEASE -
>= 4.0.0.RELEASE, < 4.1.4.RELEASE4.1.4.RELEASE -
>= 4.2.0.RELEASE, < 4.2.1.RELEASE4.2.1.RELEASE
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround provided for this vulnerability. The recommended approach is to follow the mitigation steps mentioned above.
Conclusion
The vulnerability in Spring Security allows attackers to bypass security constraints by exploiting the mishandling of URL path parameters. To mitigate this vulnerability, it is recommended to use a Servlet container that strips path parameters or upgrade to a fixed version of Spring Security. Vulert's playground can be used to check if your application is affected by this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.springframework.security:spring-security-core →
FAQ
The vulnerability affects Spring Security versions 3.2.0 - 3.2.9, 4.0.x - 4.1.3, and 4.2.0.
No, users of Apache Tomcat (all current versions) are not affected as Tomcat follows the guidance provided by the Servlet Expert group and strips path parameters from the return values of getContextPath(), getServletPath(), and getPathInfo().
Yes, users of IBM WebSphere Application Server 8.5.x are known to be affected by this vulnerability.
Users of other Servlet containers may or may not be affected depending on whether or not the handling of path parameters has been modified.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities in software using just the pom.xml file.
Related vulnerabilities
Recent vulnerabilities recorded for org.springframework.security:spring-security-core.
