Quick answers
- Is CVE-2026-40992 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40992 being exploited in the wild.
- How severe is CVE-2026-40992?
- Medium severity, with a CVSS score of 5, published 11 June 2026.
- Which products and versions are affected?
- org.springframework.boot:spring-boot-starter-mail (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.0.7; VMware Spring Boot 4.0.0 through 4.0.6, 4.0.0 through 4.0.6; 3.5.0 through 3.5.14; 3.4.0 through 3.4.16.
- Is there a fix for CVE-2026-40992?
- Yes. org.springframework.boot:spring-boot-starter-mail (Maven): upgrade to 4.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40992 attacked?
- It is attacked from the adjacent network, in a software library.
- Am I affected by CVE-2026-40992?
- Check whether you run org.springframework.boot:spring-boot-starter-mail (Maven) or VMware Spring Boot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.springframework.boot:spring-boot-starter-mail (Maven): upgrade to 4.0.7 or later
# set org.springframework.boot:spring-boot-starter-mail to 4.0.7 in your pom.xml or build.gradle
Technical details
This vulnerability is a certificate validation bypass (CWE-295) in Spring Boot's mail auto-configuration. The JavaMail library supports hostname verification via the mail.smtp.ssl.checkserveridentity property, but Spring Boot does not enable this by default. An attacker with network adjacency (e.g., on the same network segment or via compromised network infrastructure) can perform a man-in-the-middle attack by presenting a valid certificate for any domain and intercepting SMTP connections. This requires high attack complexity due to network positioning but results in potential disclosure of email content and integrity compromise. Patches are available: 4.0.7, 3.5.15, and 3.4.17+.
Affected products
- Spring Spring Boot 4.0.0 through 4.0.6
- Spring Spring Boot 3.5.0 through 3.5.14
- Spring Spring Boot 3.4.0 through 3.4.16
Identifiers
- CVE-2026-40992
- GHSA-9wxp-w4px-32vh
Timeline
- 2026-06-11: disclosed: Published to GitHub Advisory Database
- 2026-06-11: patched: Patches released: 4.0.7, 3.5.15