This vulnerability in Spring Security affects versions from 7.0.0 through 7.0.4. When applications define the servlet path using <sec:intercept-url servlet-path="/servlet-path" pattern="/endpoint/**"/>, the servlet path is excluded from the path matcher computation. As a result, authorization rules tied to the servlet path are not enforced, potentially allowing attackers to bypass authorization controls. The CVSS 3.1 vector indicates network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. There is no indication of known exploits in the wild. The vendor advisory from Red Hat does not currently confirm a patch or remediation status.

The vulnerability allows an attacker to bypass authorization rules in Spring Security when the servlet path is used in the intercept-url configuration. This can lead to unauthorized actions being performed without proper access control, impacting the integrity of the application. There is no direct confidentiality or availability impact reported.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, review and avoid using the servlet-path attribute in <sec:intercept-url> configurations or implement additional authorization checks outside of this mechanism to prevent bypass. Monitor the Red Hat advisory for updates on patches or official mitigations.