VulnerabilityPublished 22 Apr 2026

CVE-2026-22753: Spring Security · CWE-693

Affects Spring SecuritySource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
SpringSpring Security	Affected >=7.0.0 <=7.0.4	Fixed in–
Mavenorg.springframework.security/spring-security-core`pkg:maven/org.springframework.security/spring-security-core`Other threats	Affected =7.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is released, users should review their use of securityMatchers(String) and PathPatternRequestMatcher.Builder beans to ensure that servlet path prepending does not cause security filters to be bypassed. Consider alternative configurations or additional manual checks to enforce security controls on all relevant requests.

Description

CVE-2026-22753 is a vulnerability in Spring Security versions 7.0.0 through 7.0.4 where using securityMatchers(String) combined with a PathPatternRequestMatcher. Builder bean to prepend a servlet path can cause requests to bypass the intended security filter chain. This results in authentication, authorization, and other security controls not being applied to those requests as designed, potentially allowing unauthorized actions. The vulnerability has a CVSS score of 7.5, indicating high severity. No official patch or remediation guidance is currently provided by the vendor.

Impact

The impact of this vulnerability is that security controls including authentication and authorization may be bypassed for certain requests due to incorrect request matching in the filter chain. This can allow unauthorized users to perform actions that should be restricted, compromising the integrity of the application. There is no indication that confidentiality or availability are affected. No known exploits have been reported in the wild.

Summary

This vulnerability affects Spring Security versions 7.0.0 through 7.0.4. When an application uses securityMatchers(String) along with a PathPatternRequestMatcher.Builder bean to prepend a servlet path, the matching of requests to the security filter chain may fail. Consequently, the security components such as authentication and authorization may not be exercised on those requests, effectively disabling intended security controls. The issue is tracked as CVE-2026-22753 and is categorized under CWE-693 (Protection Mechanism Failure). The CVSS 3.1 base score is 7.5, reflecting a network attack vector with low complexity and no privileges or user interaction required, impacting integrity but not confidentiality or availability.

CWE-693Protection Mechanism Failure (opens in a new tab)
Pillar weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Site Tracing (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Encryption Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

spring.io/security/cve-2026-22753 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Apr 2026, 11:16 UTC

WeaknessesCWE-693

Technical details

References

Community reviews

Related threats