CVE-2026-40974: Critical severity maven/org.springframework.boot/spring-boot-autoconfigure vulnerability
Spring Boot's Cassandra auto-configuration does not perform hostname verification when establishing an SSL connection to Cassandra.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); Cassandra SSL auto-configuration. Versions that are no longer supported are also affected per vendor advisory.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Spring Bootto a version that resolves this vulnerability.Fixed in 4.0.6 - Upgrade
Upgrade
Spring Bootto a version that resolves this vulnerability.Fixed in 3.5.14 - Upgrade
Upgrade
Spring Bootto a version that resolves this vulnerability.Fixed in 3.4.16 - Upgrade
Upgrade
Spring Bootto a version that resolves this vulnerability.Fixed in 3.3.19 - Upgrade
Upgrade
Spring Bootto a version that resolves this vulnerability.Fixed in 2.7.33
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40974?
The severity of CVE-2026-40974 is considered high due to the potential for man-in-the-middle attacks when SSL connections to Cassandra are improperly validated.
How do I fix CVE-2026-40974?
To fix CVE-2026-40974, upgrade Spring Boot to version 4.0.6, 3.5.14, 3.4.16, 3.3.19, or 2.7.33.
Which versions of Spring Boot are affected by CVE-2026-40974?
Affected versions include Spring Boot 4.0.0 to 4.0.5, 3.5.0 to 3.5.13, 3.4.0 to 3.4.15, 3.3.0 to 3.3.18, and 2.7.0 to 2.7.32.
What is the impact of CVE-2026-40974 on applications?
The impact of CVE-2026-40974 allows attackers to intercept and manipulate data between a Spring Boot application and a Cassandra database due to hostname verification not being enforced.
Is there a workaround for CVE-2026-40974 before upgrading?
There is no official workaround mentioned for CVE-2026-40974; upgrading to a fixed version is strongly recommended to mitigate the risk.