VulnerabilityPublished 10 Apr 2026

CVE-2026-22750: VMware Spring Cloud Gateway · CWE-15

Affects VMware Spring Cloud GatewaySource CVE Database V5

Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 4.2.1 soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.2.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade VMware Spring Cloud Gateway to 4.2.1.

Affected software

Product	Affected	Fixed in
VMwareSpring Cloud Gateway	Affected >=4.2.0 <4.2.1	Fixed in 4.2.1
Mavenorg.springframework.cloud/spring-cloud-gateway`pkg:maven/org.springframework.cloud/spring-cloud-gateway`Other threats	Affected =4.2.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vendor advisory notes that the 4.2.x branch is no longer under open source support. Users of Spring Cloud Gateway 4.2.0 who are not enterprise customers should upgrade to any 4.2.x release newer than 4.2.0 available on Maven Central or, preferably, to the supported open source releases 5.0.2 or 5.1.1.

Description

CVE-2026-22750 is a high-severity vulnerability in VMware Spring Cloud Gateway version 4.2.0 where the configuration property spring.ssl.bundle is silently ignored, causing the default SSL configuration to be used instead. This misconfiguration can lead to a loss of intended security controls related to SSL, potentially allowing an attacker to interfere with the integrity of the system. The 4.2.x branch is no longer supported in open source, and users are advised to upgrade to newer supported versions such as 5.0.

Impact

The vulnerability causes the SSL bundle configuration to be ignored, resulting in the default SSL settings being used. This can lead to a loss of intended security controls and potentially allow attackers to compromise the integrity of communications or configurations relying on the SSL bundle. There is no reported confidentiality or availability impact. No known exploits are currently in the wild.

Summary

The vulnerability in Spring Cloud Gateway 4.2.0 involves the improper handling of the spring.ssl.bundle configuration property. When this property is set, it is silently ignored, and the system defaults to the standard SSL configuration rather than the user-defined bundle. This issue is classified under CWE-15 (Improper Initialization). The CVSS 3.1 score is 7.5 (high), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and no availability impact. The 4.2.x branch is no longer supported in open source, and users should upgrade to supported versions 5.0.2 or 5.1.1. No vendor advisory or patch links are provided, and remediation level is not specified.

CWE-15External Control of System or Configuration Setting (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
One or more system settings or configuration elements can be externally controlled by a user.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Architecture and Design
Because setting manipulation covers a diverse set of functions, any attempt at illustrating it will inevitably be incomplete. Rather than searching for a tight-knit relationship between the functions addressed in the setting manipulation category, take a step back and consider the sorts of system values that an…
Implementation · Architecture and Design
In general, do not allow user-provided or otherwise untrusted data to control sensitive values. The leverage that an attacker gains by controlling these values is not always immediately obvious, but do not underestimate the creativity of the attacker.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
XML Schema Poisoning (opens in a new tab)
Manipulate Registry Information (opens in a new tab)
Modification of Registry Run Keys (opens in a new tab)
Schema Poisoning (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

spring.io/security/cve-2026-22750 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Apr 2026, 12:30 UTC

WeaknessesCWE-15

Technical details

References

Community reviews

Related threats