# CVE-2026-22750: SSL bundle configuration silently bypassed in Spring Cloud Gateway

> Spring Cloud Gateway silently ignores custom SSL bundle configurations, forcing default settings and potentially bypassing intended security controls.

- **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:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-hwqh-2684-54fc

## What is CVE-2026-22750?

CVE-2026-22750 is a high-severity vulnerability in VMware Spring Cloud Gateway, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When configuring SSL bundles in Spring Cloud Gateway by using the configuration property spring.ssl.bundle, the configuration was silently ignored and the default SSL configuration was used instead.
Note: The 4.2.x branch is no longer under open source support. If you are using Spring Cloud Gateway 4.2.0 and are not an enterprise customer, you can upgrade to any Spring Cloud Gateway 4.2.x release newer than 4.2.0  available on Maven Centeral https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-gateway/ . Ideally if you are not an enterprise customer, you should be upgrading to 5.0.2 or 5.1.1 which are the current supported open source releases.

Weakness: CWE-15 (External Control of System or Configuration Setting)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.cloud:spring-cloud-gateway` | Maven | From 4.2.0 | 4.2.1 |
| `org.springframework.cloud:spring-cloud-gateway` | Maven | From 4.2.0 | 4.2.1 |

Products: Vmware Spring Cloud Gateway.

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

Upgrade org.springframework.cloud:spring-cloud-gateway to 4.2.1 or later.

## Is CVE-2026-22750 being exploited?

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

## Other vulnerabilities in VMware Spring Cloud Gateway

- [CVE-2026-47825](https://insights.sbomify.com/CVE-2026-47825/): Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies in certain situations (high 8.6)
- [CVE-2026-47879](https://insights.sbomify.com/CVE-2026-47879/): Spring Cloud Gateway SSRF and native file access with gRPC (high 7.7)
- [CVE-2021-22051](https://insights.sbomify.com/CVE-2021-22051/): Request injection in Spring Cloud Gateway (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22750 is a high-severity vulnerability in VMware Spring Cloud Gateway, published on 10 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-22750 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.cloud:spring-cloud-gateway (Maven): affected from 4.2.0; fixed in 4.2.1
- org.springframework.cloud:spring-cloud-gateway (Maven): affected from 4.2.0; fixed in 4.2.1

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-22750/ (Markdown: https://insights.sbomify.com/CVE-2026-22750/index.md)
```

## Sources

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

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