# CVE-2026-22754: ervlet Path Not Correctly Included in Path Matching of XML Authorization Rules

> Attackers can bypass authorization rules when servlet paths are used in XML configuration, allowing unauthorized access to protected endpoints.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** CLEANSTART-2026-LA97257, GHSA-4vrc-j85c-598c, MINI-24qv-8ppc-93fj, MINI-rx4r-jpr3-9w37, ROOT-APP-MAVEN-CVE-2026-22754

## What is CVE-2026-22754?

CVE-2026-22754 is a high-severity missing authorization vulnerability in Spring Security, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-22754?

2 open source packages ship an affected version, including org.springframework.security:spring-security-config. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-config` | Maven | From 7.0.0 | 7.0.5 |
| `org.springframework.security:spring-security-config` | Maven | From 7.0.0 | 7.0.5 |

Products: Vmware Spring Security.

## How do I fix CVE-2026-22754?

Upgrade org.springframework.security:spring-security-config to 7.0.5 or later.

## Is CVE-2026-22754 being exploited?

There is no known exploitation of CVE-2026-22754 in the wild and no public exploit code.

## Other vulnerabilities in Spring Security

- [CVE-2014-3527](https://insights.sbomify.com/CVE-2014-3527/): Authorization Bypass in Spring Security (critical 9.8)
- [CVE-2026-59354](https://insights.sbomify.com/CVE-2026-59354/): Spring Security OAuth2 Authorization Server: Insufficient validation of Dynamic Client Registration metadata (critical 9.6)
- [CVE-2026-59270](https://insights.sbomify.com/CVE-2026-59270/): Spring Security embedded UnboundID LDAP server exposes well-known administrative bind DN on all network interfaces (critical 9.4)
- [CVE-2026-22732](https://insights.sbomify.com/CVE-2026-22732/): Under Some Conditions Spring Security HTTP Headers Are not Written (critical 9.1)
- [CVE-2023-34034](https://insights.sbomify.com/CVE-2023-34034/): Access Control Bypass in Spring Security (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22754 and fix it if it is affected.

What it is: CVE-2026-22754 is a high-severity missing authorization vulnerability in Spring Security, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22754 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.security:spring-security-config (Maven): affected from 7.0.0; fixed in 7.0.5
- org.springframework.security:spring-security-config (Maven): affected from 7.0.0; fixed in 7.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22754/ (Markdown: https://insights.sbomify.com/CVE-2026-22754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22754
- OSV: https://osv.dev/vulnerability/CVE-2026-22754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22754/
Summaries are generated and may contain mistakes; the official description above is the record.