LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
6

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.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-551: Exact CWE lookup

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.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-22754 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6vmware
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-22754Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPSpring Security: Spring Security: Authorization bypass due to incorrect servlet path matching
other:Red Hat severity ratingcvssV3_1
  • 2026-04-22T06:01:11.922Z: Reported to Red Hat.
  • 2026-04-22T05:32:48.172Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SpringSpring Security7.0.0unaffected
Weakness

CWE details

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.

CWE-551 · source CWE mapping

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.