CVE-2026-22754

ervlet Path Not Correctly Included in Path Matching of XML Authorization Rules

Published Apr 22, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in Spring Security allows an attacker to bypass authorization controls because the servlet-path is omitted when computing the path matcher for XML based authorization rules. This flaw means that requests matching the specified pattern are not subjected to the intended access restrictions, potentially enabling unauthorized access to protected resources.

Affected Systems

The flaw affects applications built with Spring Security versions 7.0.0 through 7.0.4. The issue arises when the <sec:intercept-url> element uses a servlet-path attribute (e.g., servlet-path="/servlet-path") in combination with a pattern such as "/endpoint/".

Risk and Exploitability

With a CVSS score of 7.5 the vulnerability poses a high baseline risk. The EPSS score is < 1%, indicating a very low but non-zero likelihood of exploitation, and the issue is not currently listed in the CISA KEV catalog. The likely attack vector is through crafted HTTP requests that match the defined pattern, allowing attackers to locate resources that should be protected. The severity and very low EPSS suggest the risk is moderate to high and organizations using affected Spring Security versions should prioritize remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Spring Security 7.0.5 or later, which contains the path matcher fix.
  • Revise or remove any <sec:intercept-url> entries that rely on servlet-path and pattern combinations and instead use explicit path definitions.
  • Validate application functionality and run access control tests to confirm that authorization checks are enforced after the upgrade.

Generated by OpenCVE AI on April 29, 2026 at 00:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-4vrc-j85c-598c Spring Security Doesn't Correctly Include Servlet Path in Path Matching of XML Authorization Rules
History
Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Security
CPEs cpe:2.3:a:vmware:spring_security:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Security
Type Values Removed Values Added
Weaknesses CWE-284
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Security
Vendors & Products Spring
Spring spring Security
Type Values Removed Values Added
Weaknesses CWE-285
Type Values Removed Values Added
Description 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.
Title ervlet Path Not Correctly Included in Path Matching of XML Authorization Rules
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-284

    Improper Access Control

  • CWE-551

    Incorrect Behavior Order: Authorization Before Parsing and Canonicalization

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jul 15, 2026, 1:19 AM
Reserved
Jan 9, 2026, 6:55 AM
Status
Modified
Published
Apr 22, 2026, 6:16 AM
Modified
Oct 26, 2026, 10:10 PM
Severity
Important
Public date
Apr 22, 2026, 5:32 AM