CVE-2026-22750
SSL bundle configuration silently bypassed in Spring Cloud Gateway
Reported by vmware · Published April 10, 2026
spring-cloud-gateway is fixed in 4.2.1 and 4.2.0 (Maven Central)
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| org.springframework.cloud:spring-cloud-gateway | Maven Central | 4.2.1, 4.2.0 |
| Spring Cloud Gateway | VMware | 4.2.1 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| VMware | Spring Cloud Gateway | 4.2.0 |
| VMware | Spring Cloud Gateway | 4.2.0 |
Timeline
- Apr 9, 2026 CVE Published
- Apr 10, 2026 PoC Published (5 in total, the first dated here)
- Apr 10, 2026 CVE Updated
- Apr 13, 2026 Security Advisory
- May 18, 2026 EPSS Score (30 in total, the first dated here)
- Jun 25, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-22750
vulnetix vdb fixes CVE-2026-22750
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-22750/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart