CVE-2026-22750 | VMware Spring Cloud Gateway up to 4.2.0 SSL Bundle Configuration cryptographic issue

VDB-356802 · CVE-2026-22750 · GCVE-0-2026-22750 VMWARE SPRING CLOUD GATEWAY UP TO 4.2.0 SSL BUNDLE CONFIGURATION CRYPTOGRAPHIC ISSUE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.4 $0-$5k 1.88 Summaryinfo A vulnerability described as problematic has been identified in VMware Spring Cloud Gateway up to 4.2.0. The affected element is an unknown function of the component SSL Bundle Configuration Handler. The manipulation results in cryptographic issue. This vulnerability is reported as CVE-2026-22750. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended. Detailsinfo A vulnerability was found in VMware Spring Cloud Gateway up to 4.2.0. It has been classified as problematic. Affected is an unknown code block of the component SSL Bundle Configuration Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. CWE is classifying the issue as CWE-310. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes: 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. The advisory is available at spring.io. This vulnerability is traded as CVE-2026-22750 since 01/09/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 04/10/2026). This vulnerability is assigned to T1600 by the MITRE ATT&CK project. Upgrading to version 4.2.1 eliminates this vulnerability. Productinfo Type Cloud Software Vendor VMware Name Spring Cloud Gateway Version 4.0 4.1 4.2.0 License commercial Website Vendor: https://www.vmware.com/ CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.5 VulDB Meta Temp Score: 6.4 VulDB Base Score: 5.6 VulDB Temp Score: 5.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.5 CNA Vector (vmware): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Cryptographic issue CWE: CWE-310 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: Spring Cloud Gateway 4.2.1 Timelineinfo 01/09/2026 CVE reserved 04/10/2026 +90 days Advisory disclosed 04/10/2026 +0 days VulDB entry created 04/10/2026 +0 days VulDB entry last update Sourcesinfo Vendor: vmware.com Advisory: spring.io Status: Confirmed CVE: CVE-2026-22750 (🔒) GCVE (CVE): GCVE-0-2026-22750 GCVE (VulDB): GCVE-100-356802 scip Labs: https://www.scip.ch/en/?labs.20060413 Entryinfo Created: 04/10/2026 10:20 Changes: 04/10/2026 10:20 (65) Complete: 🔍 Cache ID: 99:111:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸