CVE-2026-59425
Patch Available.
This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.
Overview
Spring Cloud Gateway is a Spring project for building API gateways. It routes incoming HTTP requests to backend services and applies filters to them, such as the JsonToGrpc filter, which turns a JSON request into a call to a gRPC service.
A denial of service vulnerability (CVE-2026-59425) has been identified in the JsonToGrpc filter of Spring Cloud Gateway, which allows unauthenticated attackers to exhaust the gateway's sockets and channel resources by sending repeated requests to a route that uses the filter.
Per OWASP: The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed.
This issue affects multiple versions of Spring Cloud Gateway.
Details
Module Info
- Product: Spring Cloud Gateway
- Affected packages:
org.springframework.cloud:spring-cloud-gateway-server,org.springframework.cloud:spring-cloud-gateway-server-webflux - Affected versions:
org.springframework.cloud:spring-cloud-gateway-server: >=3.1.4 <=3.1.14, >=4.2.0 <=4.2.10, >=4.3.0 <=4.3.6org.springframework.cloud:spring-cloud-gateway-server-webflux: >=5.0.0 <=5.0.4- GitHub repository: https://github.com/spring-cloud/spring-cloud-gateway
- Published packages:
- https://central.sonatype.com/artifact/org.springframework.cloud/spring-cloud-gateway-server
- https://central.sonatype.com/artifact/org.springframework.cloud/spring-cloud-gateway-server-webflux
- Package manager: Maven
- Fixed in:
- OSS Spring Cloud Gateway 5.0.5
- NES for Spring Cloud Gateway
Vulnerability Info
This High-severity vulnerability is found in the spring-cloud-gateway-server and spring-cloud-gateway-server-webflux packages in multiple versions of Spring Cloud Gateway. The CVSS 3.1 base score is 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
JsonToGrpcGatewayFilterFactory decorates the response of every request that matches a route configured with the JsonToGrpc filter. The decorator's constructor prepares the gRPC call, and to do so it opens a new Netty-backed gRPC ManagedChannel to the route's host and port:
private ManagedChannel createChannel() {
URI requestURI = ((Route) exchange.getAttributes().get(ServerWebExchangeUtils.GATEWAY_ROUTE_ATTR)).getUri();
return createChannelChannel(requestURI.getHost(), requestURI.getPort());
}
// We are creating this on every call, should optimize?
private ManagedChannel createChannelChannel(String host, int port) {
NettyChannelBuilder nettyChannelBuilder = NettyChannelBuilder.forAddress(host, port);
try {
return grpcSslConfigurer.configureSsl(nettyChannelBuilder);
}
catch (SSLException e) {
throw new RuntimeException(e);
}
}The channel is used for a single unary call and is then dropped. Nothing calls shutdown() on it, it is not cached for reuse, and the factory does not close channels when the application context stops. Its socket and channel resources stay open after the request completes. An unauthenticated client that can reach such a route only has to send requests in a loop: every request leaves another open channel behind, until the gateway exhausts its sockets and channel resources and can no longer serve legitimate traffic. Applications are affected only if they expose a route that uses the JsonToGrpc filter.
Mitigation
Only recent versions of Spring Cloud Gateway receive community support. Older lines are End-of-Life and will not receive public updates to address this issue.
Users of the affected components should apply one of the following mitigations:
- Upgrade to a currently supported version of Spring Cloud Gateway.
- Leverage a commercial support partner like HeroDevs for post-EOL security support.
Credits
- Liyi (finder)
- Ziyue (finder)
- Strick (finder)
- Maurice (finder)
- Chenchen (finder)