CVE-2026-22750
Vmware Spring Cloud Gateway 4.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-22750 is a high-severity External Control of System or Configuration Setting (CWE-15) vulnerability in Vmware Spring Cloud Gateway. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception by PATH Environment Variable (T1574.007); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22750 is a vulnerability in Spring Cloud Gateway where the configuration property spring.ssl.bundle for SSL bundles is silently ignored, causing the application to fall back to the default SSL configuration instead. This issue primarily affects the 4.2.x branch, including version 4.2.0, which is no longer under open source support. The vulnerability is classified under CWE-15 (External Control of System or Configuration Setting) with a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high severity due to its network accessibility and integrity impact.
Remote, unauthenticated attackers can exploit this vulnerability with low complexity and no user interaction. By leveraging the ignored custom SSL bundle configuration, attackers can achieve high integrity impact, potentially allowing unauthorized modification of data in transit or related to the gateway's SSL handling.
The Spring advisory at https://spring.io/security/cve-2026-22750 recommends upgrading from Spring Cloud Gateway 4.2.0 to any newer 4.2.x release available on Maven Central (https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-gateway/). For non-enterprise users, the ideal mitigation is to upgrade to the supported open source releases 5.0.2 or 5.1.1.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-21330
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access to configuration resources so external parties cannot alter them.
Enforces documented access restrictions on all changes to system configuration, directly blocking unauthorized external control of settings.
Limits privileges to the minimum needed, reducing the set of users who can externally modify configuration.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened configuration baselines and change controls directly limit external manipulation of settings.
Formal change and exception management catches externally driven configuration alterations.
Least-privilege access policies reduce unauthorized external modification of configuration values.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration management directly prevents external tampering with system settings.
Access rights assignment determines who may change system settings.
Privileged access rights reduce the number of users who can alter configuration.
Information access restriction limits who can view or modify configuration data.
Change management enforces controlled, authorized modifications to settings.
Access control policies underpin the technical restrictions on configuration changes.