Server impersonation via disabled hostname verification
Published Apr 27, 2026 · Updated Apr 27, 2026
Improper certificate validation in Spring Boot 4.0.0 through 4.0.5 allows man-in-the-middle attackers to impersonate Elasticsearch servers. The Elasticsearch auto-configuration applies an SSL bundle without checking that the peer certificate's hostname matches the configured server. Exploitation requires an SSL-bundle configuration, control of an adjacent network path, and a certificate trusted by the bundle; successful interception exposes Elasticsearch traffic to reading or modification.
Summary
What happened
Improper certificate validation in Spring Boot 4.0.0 through 4.0.5 allows man-in-the-middle attackers to impersonate Elasticsearch servers. The Elasticsearch auto-configuration applies an SSL bundle without checking that the peer certificate's hostname matches the configured server. Exploitation requires an SSL-bundle configuration, control of an adjacent network path, and a certificate trusted by the bundle; successful interception exposes Elasticsearch traffic to reading or modification.
The record
- CVE
- CVE-2026-40970
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- Spring
- Product
- Spring Boot
- Classifications
- CWE-295, T1557
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.0.0 <4.0.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo