Spring Cloud Gateway's SSL bundle configuration silently bypassed

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-22750: 0.22% estimated exploitation activity in the next 30 days; percentile 12.27 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

10 Apr 2026, 09:31 UTC

Last modified by the source

14 Apr 2026, 18:27 UTC

Source last checked

26 Oct 2026, 16:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hwqh-2684-54fc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22750

Advisory: Spring Cloud Gateway's SSL bundle configuration silently bypassed
IDs: CVE-2026-22750, GHSA-hwqh-2684-54fc
Record: https://patchnext.com/advisories/cve-2026-22750 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.springframework.cloud:spring-cloud-gateway 4.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.cloud:spring-cloud-gateway: affected >= 4.2.0, <= 4.2.0; fixed in 4.2.1

## Suggested inspection (read-only)
- Maven org.springframework.cloud:spring-cloud-gateway: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework.cloud:spring-cloud-gateway.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-hwqh-2684-54fc (GitHub-reviewed advisory GHSA-hwqh-2684-54fc lists affected ranges: Maven org.springframework.cloud:spring-cloud-gateway >=4.2.0 <=4.2.0)

Commands are suggestions: review each one before running it.