CVE-2026-22754: ervlet Path Not Correctly Included in Path Matching of XML Authorization Rules
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.
Security readout for executives and security teams
Plain-English summary
Some Spring Security applications may fail to enforce intended access rules when XML authorization uses a servlet-path plus endpoint pattern. Requests that should be blocked could be allowed, causing an authorization bypass. The issue is high severity because it can affect integrity without credentials or user interaction, but evidence provided does not show active exploitation.
Executive priority
Treat as a high-priority application security issue for teams using recent Spring Security 7.0.x. Focus first on internet-facing or sensitive business workflows where authorization errors could permit unauthorized changes or access to restricted functions.
Technical view
CVE-2026-22754 affects Spring Security 7.0.0 through 7.0.4. When XML uses <sec:intercept-url servlet-path="/servlet-path" pattern="/endpoint/**"/>, the servlet path is not included in path matching, so related authorization rules may not execute. CVSS 3.1 is 7.5: network exploitable, low complexity, no privileges, integrity impact only.
Likely exposure
Exposure is likely limited to applications running Spring Security 7.0.0 through 7.0.4 that use XML <sec:intercept-url> rules with the servlet-path attribute. Applications not using that configuration pattern are not shown as affected by the supplied sources.
Exploitation context
The supplied bundle states KEV is false and provides no cited evidence of active exploitation. The issue is remotely reachable where affected applications expose protected web endpoints, but the sources do not provide exploit status beyond the authorization bypass description.
Researcher notes
The key condition is configuration-specific: XML authorization with servlet-path-driven path matching. The provided affected range says 7.0.0 through 7.0.4, while the affected object only lists 7.0.0, so use the advisory text as primary scope and verify vendor updates.
Mitigation direction
Inventory Spring Security versions across applications.
Prioritize Spring Security 7.0.0 through 7.0.4 deployments.
Review Spring’s advisory for official fixed versions or mitigations.
Identify XML authorization rules using servlet-path on intercept-url.
Apply vendor guidance, then retest affected authorization paths.
Validation and detection
Search configurations for <sec:intercept-url> entries using servlet-path.
Confirm whether deployed Spring Security versions are 7.0.0 through 7.0.4.
Review tests covering servlet-path plus pattern authorization decisions.
Verify protected endpoints deny unauthorized access after remediation.
Check Red Hat VEX data if relying on Red Hat-packaged components.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.