Spring SecurityFramework / library · VMware
CVE-2026-22753
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedVulnerability 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a security bypass vulnerability in Spring Security 7.0.0-7.0.4 where using securityMatchers(String) with a PathPatternRequestMatcher.Builder bean and servlet path prepending causes request matching to fail. This prevents the security filter chain from being applied to intended requests, effectively rendering authentication, authorization, and other security controls inactive for affected endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring SecurityFramework / library
>= 7.0.0, < 7.0.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Spring Security version in useInspect your project's dependency management file (Maven pom.xml, Gradle build.gradle) or list the spring-security-core JAR file to determine the exact version. For runtime inspection, you can use your dependency management tool or check the manifest file within the spring-security-core JAR.Affected if The version is 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.4 (any version >= 7.0.0 and < 7.0.5)
-
Determine if securityMatchers is used with PathPatternRequestMatcher.BuilderReview your Spring Security configuration classes that define security filter chains. Look for usages of securityMatchers(String) or securityMatchers(PathPattern) in combination with a bean of type PathPatternRequestMatcher.Builder.Affected if Your code creates a PathPatternRequestMatcher.Builder bean and passes it to securityMatchers using a String pattern
-
Check if servlet path prepending is enabledExamine your application configuration (application.properties or application.yml) for the server.servlet.path property, or programmatically check if servlet path handling is enabled in your web server configuration.Affected if Servlet path prepending is configured via server.servlet.path or equivalent configuration
-
Verify the security filter chain is actually being appliedSend a test request to an endpoint protected by the affected securityMatchers configuration and confirm that authentication and authorization rules are enforced as expected. Check security logs if available.Affected if The protected endpoint responds without applying authentication/authorization controls, indicating the filter chain was bypassed
You are affected if you use Spring Security versions 7.0.0 through 7.0.4 in combination with securityMatchers using a PathPatternRequestMatcher.Builder bean and have servlet path prepending enabled, resulting in security controls not being applied to intended endpoints.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.5
Upgrade Spring Security to version 7.0.5 or later. Alternatively, review and refactor the use of PathPatternRequestMatcher.Builder with securityMatchers to ensure proper request matching behavior.
Spring Security 7.0.5
- 1. Locate your project's dependency management file (pom.xml for Maven or build.gradle for Gradle)
- 2. Find the Spring Security dependency declaration
- 3. Change the Spring Security version from 7.0.0-7.0.4 to 7.0.5 or later (e.g., 7.0.5)
- 4. Rebuild your project to apply the version change
- 5. Test your application to verify that securityMatchers with PathPatternRequestMatcher.Builder now correctly enforce authentication, authorization, and other security controls on intended requests
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22753 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data