dbcve.org
Spring Cloud GatewayFramework / library · VMware

CVE-2026-22750

HIGH · 7.5 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Spring Cloud Gateway, the spring.ssl.bundle configuration property is silently ignored during SSL setup, causing the framework to fall back to default SSL settings instead of applying user-defined bundle configurations. This bypass means SSL hardening intended by administrators is not applied, potentially allowing weaker cipher suites or incorrect certificate validation.

MitigationUpgrade Spring Cloud Gateway to version 5.0.2 or 5.1.1 (or a newer 4.2.x release if enterprise support applies) to ensure SSL bundle configurations are properly honored.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Cloud GatewayFramework / library
Affected:= 4.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Cloud Gateway version
    Check your project's dependencies or runtime environment to confirm the exact version of Spring Cloud Gateway in use. Common locations: Maven pom.xml, Gradle build.gradle, or the gateway application's manifest/BOM file.
    Affected if The installed version is exactly 4.2.0
  2. Locate SSL bundle configuration
    Search configuration files (application.yml, application.properties, or externalized config) for properties matching spring.ssl.bundle or spring.ssl.bundles. Check all profiles and configuration sources.
    Affected if spring.ssl.bundle or spring.ssl.bundles configuration is defined in your configuration files
  3. Verify SSL is enabled in the gateway
    Inspect your gateway configuration for SSL-enabled endpoints, server.ssl configuration, or any references to TLS/SSL in the routing or server settings.
    Affected if SSL/TLS is enabled and the gateway is configured to handle HTTPS traffic
  4. Confirm SSL bundle is actually applied
    Review application logs at startup for SSL initialization messages, or use runtime diagnostics (such as examining the actual SSL context or cipher suites in use) to verify the configured bundle is being loaded rather than default settings.
    Affected if The spring.ssl.bundle configuration exists but is not being honored (SSL falls back to defaults instead of using the bundle)

You are affected if running Spring Cloud Gateway version 4.2.0 with spring.ssl.bundle configuration present while SSL is enabled, because the bundle settings are silently ignored and defaults are used instead.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Cloud Gateway to version 5.0.2 or 5.1.1 (or a newer 4.2.x release if enterprise support applies) to ensure SSL bundle configurations are properly honored.

Recommended fix High confidence

Upgrade to Spring Cloud Gateway 4.2.x > 4.2.0, ideally 5.0.2 or 5.1.1

  1. 1. Identify the current Spring Cloud Gateway version in your project (check pom.xml or build.gradle for spring-cloud-gateway version)
  2. 2. If using version 4.2.0, upgrade to a newer 4.2.x release (e.g., 4.2.1, 4.2.2, etc.) available on Maven Central, or ideally upgrade to 5.0.2 or 5.1.1
  3. 3. Update the version in your build configuration (pom.xml or build.gradle)
  4. 4. Rebuild and redeploy the application
  5. 5. Verify that the spring.ssl.bundle configuration is now properly applied and not silently ignored
Caveat Major version upgrades (4.x to 5.x) may introduce breaking changes; review Spring Cloud Gateway 5.x release notes for migration guidance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Cloud Gateway Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22750 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data