CVE-2026-40970 Spring Boot's Elasticsearch auto-configuration doesn't perform hostname verification when connecting to the Elasticsearch server.

Medium 5.0 Published Updated

Attackers can bypass SSL hostname verification in Spring Boot Elasticsearch connections, enabling man-in-the-middle attacks to intercept or read sensitive data.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-40970?

CVE-2026-40970 is a medium-severity vulnerability in Spring Boot, published on 27 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

When configured to use an SSL bundle, Spring Boot's Elasticsearch auto-configuration does not perform hostname verification when connecting to the Elasticsearch server.

Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.

Weakness: CWE-295

Which versions are affected by CVE-2026-40970?

2 open source packages ship an affected version, including org.springframework.boot:spring-boot-elasticsearch. It affects 1 product.

PackageAffectedFixed in
org.springframework.boot:spring-boot-elasticsearch MavenFrom 4.0.04.0.6
org.springframework.boot:spring-boot-elasticsearch MavenFrom 4.0.04.0.6

Products include Vmware Spring Boot.

How do I fix CVE-2026-40970?

Upgrade org.springframework.boot:spring-boot-elasticsearch to 4.0.6 or later.

Is CVE-2026-40970 being exploited?

There is no known exploitation of CVE-2026-40970 in the wild and no public exploit code.

Sources

Also known as GHSA-c96x-rpm4-349p.

Is CVE-2026-40970 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free