CVE-2026-59373

Improper Certificate Validation
Affects
Spring Boot
in
Spring
No items found.
Versions
>=4.1.0 <=4.1.2, >=4.0.0 <=4.0.9, >=3.5.0 <=3.5.17, >=3.0.0 <=3.4.18, <=2.7.35

Patch Available.

Exclamation circle icon
Patch Available

This Vulnerability has been fixed in the Never-Ending Support (NES) version offered by HeroDevs.

Overview

Spring Boot is an opinionated framework for building stand-alone, production-ready Spring applications, providing auto-configuration that wires up infrastructure such as data stores, messaging and web servers from application properties.

An improper certificate validation vulnerability (CVE-2026-59373) has been identified in Spring Boot's Redis auto-configuration for the Jedis client, which allows attackers positioned on the network path to impersonate the Redis server and read or modify the traffic of an SSL connection. Spring Boot enables SSL for Jedis connections without turning on TLS hostname verification, so any certificate trusted by the JVM is accepted for any Redis host.

Per CWE: The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.

This issue affects multiple versions of Spring Boot.

Details

Module Info

Vulnerability Info

This Medium-severity vulnerability is found in the org.springframework.boot:spring-boot-autoconfigure package in multiple versions of Spring Boot (and in org.springframework.boot:spring-boot-data-redis from Spring Boot 4.0). When an application uses the Jedis client and enables SSL for Redis, either through spring.data.redis.ssl.* (spring.redis.ssl on older lines) or by giving a rediss:// URL, Spring Boot's JedisConnectionConfiguration switches the client to SSL but never sets an endpoint identification algorithm on the TLS connection.

Hostname verification in the JDK's TLS stack is only performed when SSLParameters.setEndpointIdentificationAlgorithm("HTTPS") (or an explicit hostname verifier) is configured. Jedis does not add one on its own, so the connection checks only that the server's certificate chains to a trusted authority, not that it was issued for the Redis host the application is connecting to.

In the SSL bundle path, the auto-configuration builds SSLParameters from the bundle's ciphers and protocols only:

private void applySslIfNeeded(JedisClientConfigurationBuilder builder) {
    SslBundle sslBundle = getSslBundle();
    if (sslBundle == null) {
        return;
    }
    JedisSslClientConfigurationBuilder sslBuilder = builder.useSsl();
    sslBuilder.sslSocketFactory(sslBundle.createSslContext().getSocketFactory());
    SslOptions sslOptions = sslBundle.getOptions();
    SSLParameters sslParameters = new SSLParameters();
    PropertyMapper map = PropertyMapper.get().alwaysApplyingWhenNonNull();
    map.from(sslOptions.getCiphers()).to(sslParameters::setCipherSuites);
    map.from(sslOptions.getEnabledProtocols()).to(sslParameters::setProtocols);
    sslBuilder.sslParameters(sslParameters);
}

In the URL path, a rediss:// URL only turns SSL on, with no SSL parameters at all:

private void customizeConfigurationFromUrl(JedisClientConfiguration.JedisClientConfigurationBuilder builder) {
    if (urlUsesSsl()) {
        builder.useSsl();
    }
}

Older lines that predate SSL bundles behave the same way: they call builder.useSsl() (or factory.setUseSsl(true)) when SSL is requested and never configure hostname verification. An attacker on an adjacent network who can intercept the connection and present any certificate signed by a CA in the application's trust store (for example a certificate issued for a different host) is therefore accepted as the Redis server. The attacker can then capture the Redis password sent during authentication, read cached or session data, and tamper with or drop commands and replies.

Mitigation

Only recent versions of Spring Boot 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 Boot.
  • Leverage a commercial support partner like HeroDevs for post-EOL security support.

Credits

  • Mike Read (finder)
  • h1ei1 (finder)
  • LiZhiyao from BUPT (finder)
  • Srinivasa Challa (finder)
Vulnerability Details
Severity
Level
CVSS Assessment
Low
>=0 <4
Medium
>=4 <6
High
>=6 <8
Critical
>=8 <10
Medium
ID
CVE-2026-59373
PROJECT Affected
Spring Boot
Versions Affected
>=4.1.0 <=4.1.2, >=4.0.0 <=4.0.9, >=3.5.0 <=3.5.17, >=3.0.0 <=3.4.18, <=2.7.35
NES Versions Affected
Published date
November 20, 2026
≈ Fix date
Category
Improper Certificate Validation
Vex Document
Download VEXHow do I use it?
Sign up for the latest vulnerability alerts fixed in
NES for Spring
Rss feed icon
Subscribe via RSS
or

By submitting the form I acknowledge receipt of our Privacy Policy.

Thanks for signing up for our Newsletter! We look forward to connecting with you.
Oops! Something went wrong while submitting the form.