CVE-2026-22754 json
ervlet Path Not Correctly Included in Path Matching of XML Authorization Rules
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also GHSA-4vrc-j85c-598c , EUVD-2026-24612
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.springframework.security:spring-security-config 7.0.5
- vmware spring_security 7.0.5
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-22754 updated cvss 7.5
Spring Security: Spring Security: Authorization bypass due to incorrect servlet path matching
-
Red Hat OpenShift Developer Tools and Services jenkins, ocp-tools-4/jenkins-rhel8, ocp-tools-4/jenkins-rhel9 Red Hat build of Apache Camel - HawtIO 4 spring-security-core Red Hat build of Apache Camel for Spring Boot 4 spring-security-core Red Hat build of Quarkus quarkus-spring-security-core-api Red Hat Data Grid 8 spring-security-core Red Hat Fuse 7 spring-security-core, org.apache.servicemix.bundles.spring-security-corenot affected: vulnerable code not present
+6 more productsfewer
Red Hat JBoss Enterprise Application Platform 7 spring-security-core Red Hat JBoss Enterprise Application Platform 8 spring-security-core, quarkus-spring-security-core-api Red Hat JBoss Enterprise Application Platform Expansion Pack spring-security-core, quarkus-spring-security-core-api Red Hat OpenShift Dev Spaces devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Process Automation 7 spring-security-core Red Hat Single Sign-On 7 spring-security-core
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.security:spring-security-config | >=7.0.0, <7.0.5 |
7.0.5 |
Affected products
- Spring Spring Security
- Red Hat OpenShift Developer Tools and Services
- Red Hat Red Hat build of Apache Camel for Spring Boot 4
- Red Hat Red Hat build of Apache Camel - HawtIO 4
- Red Hat Red Hat build of Quarkus
- Red Hat Red Hat Data Grid 8
- Red Hat Red Hat Fuse 7
- Red Hat Red Hat JBoss Enterprise Application Platform 7
- Red Hat Red Hat JBoss Enterprise Application Platform 8
- Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
- Red Hat Red Hat OpenShift Dev Spaces
- Red Hat Red Hat Process Automation 7
- Red Hat Red Hat Single Sign-On 7
Classification
- Weakness
- Technology feeds
References
-
spring.io
/security/cve-2026-22754
web, mitigation, vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-22754
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2460489
issue-tracking
- security.access.redhat.com /data/csaf/v2/vex/2026/cve-2026-22754.json
-
nvd.nist.gov
/vuln/detail/CVE-2026-22754
advisory
-
github.com
/spring-projects/spring-security
package
Sources
- CVE List CVE-2026-22754
- GitHub Advisory GHSA-4vrc-j85c-598c
- NVD CVE-2026-22754
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.