{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-22750", "assignerOrgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "state": "PUBLISHED", "assignerShortName": "vmware", "dateReserved": "2026-01-09T06:55:03.990Z", "datePublished": "2026-04-10T07:32:31.260Z", "dateUpdated": "2026-04-10T07:32:31.260Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "dcf2e128-44bd-42ed-91e8-88f912c1401d", "shortName": "vmware", "dateUpdated": "2026-04-10T07:32:31.260Z"}, "title": "SSL bundle configuration silently bypassed in Spring Cloud Gateway", "datePublic": "2026-04-09T14:15:00.000Z", "affected": [{"vendor": "VMware", "product": "Spring Cloud Gateway", "packageName": "Spring Cloud Gateway", "versions": [{"status": "affected", "version": "4.2.0", "lessThan": "4.2.1", "versionType": "ENTERPRISE"}], "defaultStatus": "unaffected"}], "descriptions": [{"lang": "en", "value": "When configuring SSL bundles in Spring Cloud Gateway by using the configuration property\u00a0spring.ssl.bundle, the configuration was silently ignored and the default SSL configuration was used instead.\nNote: The\u00a04.2.x\u00a0branch is no longer under open source support. If you are using Spring Cloud Gateway\u00a04.2.0\u00a0and are not an enterprise customer, you can upgrade to any Spring Cloud Gateway\u00a04.2.x\u00a0release newer than\u00a04.2.0\u00a0 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\u00a05.0.2\u00a0or\u00a05.1.1\u00a0which are the current supported open source releases.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "When configuring SSL bundles in Spring Cloud Gateway by using the configuration property&nbsp;<code>spring.ssl.bundle</code>, the configuration was silently ignored and the default SSL configuration was used instead.<br>Note: The&nbsp;<code>4.2.x</code>&nbsp;branch is no longer under open source support. If you are using Spring Cloud Gateway&nbsp;<code>4.2.0</code>&nbsp;and are not an enterprise customer, you can upgrade to any Spring Cloud Gateway&nbsp;<code>4.2.x</code>&nbsp;release newer than&nbsp;<code>4.2.0</code>&nbsp;<a href=\"https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-gateway/\">available on Maven Centeral</a>. Ideally if you are not an enterprise customer, you should be upgrading to&nbsp;<code>5.0.2</code>&nbsp;or&nbsp;<code>5.1.1</code>&nbsp;which are the current supported open source releases."}]}], "references": [{"url": "https://spring.io/security/cve-2026-22750"}], "metrics": [{"format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}], "cvssV3_1": {"version": "3.1", "attackVector": "NETWORK", "attackComplexity": "LOW", "privilegesRequired": "NONE", "userInteraction": "NONE", "scope": "UNCHANGED", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "availabilityImpact": "NONE", "baseSeverity": "HIGH", "baseScore": 7.5, "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"}}], "source": {"discovery": "UNKNOWN"}, "x_generator": {"engine": "Vulnogram 1.0.1"}}}}

{}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "When configuring SSL bundles in Spring Cloud Gateway by using the configuration property\u00a0spring.ssl.bundle, the configuration was silently ignored and the default SSL configuration was used instead.\nNote: The\u00a04.2.x\u00a0branch is no longer under open source support. If you are using Spring Cloud Gateway\u00a04.2.0\u00a0and are not an enterprise customer, you can upgrade to any Spring Cloud Gateway\u00a04.2.x\u00a0release newer than\u00a04.2.0\u00a0 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\u00a05.0.2\u00a0or\u00a05.1.1\u00a0which are the current supported open source releases."}], "id": "CVE-2026-22750", "lastModified": "2026-04-10T08:16:24.787", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "version": "3.1"}, "exploitabilityScore": 3.9, "impactScore": 3.6, "source": "security@vmware.com", "type": "Secondary"}]}, "published": "2026-04-10T08:16:24.787", "references": [{"source": "security@vmware.com", "url": "https://spring.io/security/cve-2026-22750"}], "sourceIdentifier": "security@vmware.com", "vulnStatus": "Received"}

{}

{"analysis": {"en": {"generated_at": "2026-04-10T09:23:27.003581+00:00", "value": {"mitigation_remediation": ["Upgrade to Spring Cloud Gateway 5.0.2 or 5.1.1 if you are not on a supported enterprise version", "If you are using the 4.2.x branch, upgrade to any release newer than 4.2.0 available on Maven Central", "After upgrading, verify that the spring.ssl.bundle configuration is accepted and that the intended certificates and key stores are in use", "Continue to monitor gateway logs for TLS negotiation to confirm secure operation"], "summary": {"action": "Immediate Patch", "impact": "Misconfigured TLS due to ignored SSL bundle configuration"}, "threat_synthesis": {"affected_systems": "This issue affects VMware Spring Cloud Gateway, specifically versions within the 4.2.x branch and the 5.x releases that support the spring.ssl.bundle property. Users of the unsupported 4.2.0 release are particularly at risk if they believe their custom SSL bundle is active.", "description_and_impact": "The vulnerability occurs when the configuration property used to specify SSL bundles in Spring Cloud Gateway is silently ignored, causing the gateway to fall back to its default SSL settings. This misconfiguration means that administrators cannot enforce the intended TLS certificates, key stores, or protocol restrictions. As a result, the gateway may operate with weaker or default TLS settings, potentially exposing traffic to downgrade or man\u2011in\u2011the\u2011middle attacks and bypassing intended authentication or encryption policies.", "risk_and_exploitability": "The CVSS score of 7.5 categorizes the problem as medium to high severity. Although EPSS data is not available and the vulnerability is not listed in CISA\u2019s KEV catalog, the fact that the configuration is silently ignored makes it exploitable by any party able to influence the gateway\u2019s application configuration or by attackers who rely on the default, potentially insecure, TLS settings. The risk is therefore significant for deployments that depend on the gateway to enforce strict SSL policies."}}}}, "created": "2026-04-10T09:26:27.166364+00:00", "updated": "2026-04-10T09:26:27.166392+00:00", "vendors": [], "weaknesses": ["CWE-347", "CWE-610"]}