# CVE-2026-22753: Spring Security Doesn't Correctly Include Servlet Path in Path Matching of HttpSecurity#securityMatchers

Source: https://junglewise.ai/threats/cve-2026-22753-spring-security-doesn-t-correctly-include-servlet-path-in-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-22  
License: CC BY 4.0 with a link back

CVE-2026-22753 · Severity: high · CVSS 7.5 · Published 2026-04-22

Vulnerability in Spring Spring Security. If an application is using securityMatchers(String) and a PathPatternRequestMatcher.Builder bean to prepend a servlet path, matching requests to that filter chain may fail and its related security components will not be exercised as intended by the application. This can lead to the authentication, authorization, and other security controls being rendered inactive on intended requests.This issue affects Spring Security: from 7.0.0 through 7.0.4.

Technologies: [org.springframework.security:spring-security-config (Maven)](https://junglewise.ai/threats/technologies/org-springframework-security-spring-security-config), [VMware Spring Security](https://junglewise.ai/threats/technologies/spring-security). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven), [VMware](https://junglewise.ai/threats/vendors/vmware).

## Quick answers

**Is CVE-2026-22753 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-22753 being exploited in the wild.

**How severe is CVE-2026-22753?** High severity, with a CVSS score of 7.5, published 22 April 2026.

**Which products and versions are affected?** org.springframework.security:spring-security-config (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.5.

**Is there a fix for CVE-2026-22753?** Yes. org.springframework.security:spring-security-config (Maven): upgrade to 7.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-22753?** Check whether you run org.springframework.security:spring-security-config (Maven) or VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.springframework.security:spring-security-config (Maven): upgrade to 7.0.5 or later

  ```sh
  # set org.springframework.security:spring-security-config to 7.0.5 in your pom.xml or build.gradle
  ```


## Affected products

- org.springframework.security:spring-security-config (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.5
- VMware Spring Security

## Identifiers

- CVE-2026-22753
- GHSA-4wrg-8wpc-h923

## Related threats

- [Spring Security InetAddressMatchers IP classification bypass](https://junglewise.ai/threats/cve-2026-59277-spring-security-inetaddressmatchers-ip-classification-bypass)
- [Spring Security timing attack on security-sensitive string comparison](https://junglewise.ai/threats/cve-2026-59276-spring-security-timing-attack-on-security-sensitive-string)
- [Spring Security OAuth2 Authorization Server metadata validation in Dynamic Client Registration](https://junglewise.ai/threats/cve-2026-59354-spring-security-oauth2-authorization-server-metadata-validation)
- [Spring Security embedded UnboundID LDAP server authentication bypass](https://junglewise.ai/threats/cve-2026-59270-spring-security-embedded-unboundid-ldap-server-authentication)
- [Spring Security WebAuthn user verification bypass in distributed sessions](https://junglewise.ai/threats/cve-2026-47841-spring-security-webauthn-user-verification-bypass-in-distributed)