CVE-2026-40970 is an improper TLS certificate hostname validation vulnerability in Spring Boot Elasticsearch auto-configuration. In Spring Boot versions 4.0.0 through 4.0.5, configuring the Elasticsearch client with an SSL bundle causes the auto-configured connection not to perform TLS hostname verification of the Elasticsearch server certificate. Consequently, a certificate that chains to a trusted authority but is issued for a different hostname may be accepted.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An Elasticsearch auto-configuration vulnerability involving TLS hostname verification disablement, mentioned as also fixed in Spring Boot 4.0.6.
A vulnerability in Spring Boot where Elasticsearch auto-configuration with an SSL bundle disables TLS hostname verification.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.