dbcve.org
Spring SecurityFramework / library · VMware

CVE-2026-22754

HIGH · 7.5 CVSS v3.1 Published 2026-04-22
Fix available
A fix is available. Upgrade to 7.0.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability in Spring Spring Security. If an application uses <sec:intercept-url servlet-path="/servlet-path" pattern="/endpoint/**"/> to define the servlet path for computing a path matcher, then the servlet path is not included and the related authorization rules are not exercised. This can lead to an authorization bypass.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 confidence

In Spring Security 7.0.0-7.0.4, when using the servlet-path attribute in <sec:intercept-url> configuration to define a servlet path for path matching, the servlet path is incorrectly omitted from the path matching computation. This causes authorization rules defined with servlet-path to be bypassed, allowing unauthenticated or unauthorized access to protected endpoints.

MitigationReview all <sec:intercept-url> configurations using servlet-path attribute and verify authorization is working as expected. Consider upgrading to a patched version when available, or implement compensating controls such as additional filter-based authorization 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
Affected:>= 7.0.0, < 7.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Security version
    Inspect your project build file (pom.xml, build.gradle) or runtime dependency management to find the Spring Security version in use
    Affected if The installed version is between 7.0.0 and 7.0.4 inclusive
  2. Locate Spring Security XML configuration
    Search for XML configuration files containing <sec:http> or <sec:intercept-url> elements, typically in WEB-INF/spring-security.xml or similar configuration files
    Affected if XML-based security configuration files exist in the project
  3. Check for servlet-path attribute usage
    Within the XML configuration files, inspect <sec:intercept-url> elements for the presence of the servlet-path attribute
    Affected if The servlet-path attribute is defined on any <sec:intercept-url> element
  4. Verify authorization behavior
    Test protected endpoints defined with servlet-path to confirm authorization rules are actually being applied (e.g., access an endpoint that should require authentication but is accessible without credentials)
    Affected if Endpoints protected by intercept-url rules with servlet-path are accessible when they should be restricted

A user is affected if their application runs Spring Security 7.0.0-7.0.4 AND uses the servlet-path attribute in <sec:intercept-url> configuration, causing authorization rules to be bypassed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.5 or later
Fixed in 7.0.5
Interim mitigation

Review all <sec:intercept-url> configurations using servlet-path attribute and verify authorization is working as expected. Consider upgrading to a patched version when available, or implement compensating controls such as additional filter-based authorization for affected endpoints.

Recommended fix High confidence

7.0.5

  1. Identify your build configuration file (pom.xml for Maven or build.gradle for Gradle)
  2. Locate the Spring Security dependency declaration
  3. Update the spring-security-version property or the direct dependency version to 7.0.5 or later
  4. Run your build tool to fetch the updated dependency (e.g., mvn clean install or ./gradlew build)
  5. Rebuild and test your application to ensure authorization rules are now correctly applied
  6. Verify that the <sec:intercept-url> configuration with servlet-path now properly enforces access control
Caveat Point releases within the same minor version typically do not include breaking changes; however, review the Spring Security 7.0.5 release notes for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Security Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22754 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22754 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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