CVE-2026-40992 json
Mail Auto-Configuration Does Not Enable SSL Hostname Verification
published 4mo ago modified 2mo ago also GHSA-9wxp-w4px-32vh , EUVD-2026-36203
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
Spring Boot's Mail auto-configuration does not enable hostname verification. Applications that set the relevant JavaMail property, such as spring.mail.properties.mail.smtp.ssl.checkserveridentity=true, are not affected.
Affected versions: Spring Boot 4.0.0 through 4.0.6; 3.5.0 through 3.5.14; 3.4.0 through 3.4.16.
Patch / fix
- maven org.springframework.boot:spring-boot-starter-mail 3.5.15, 4.0.7
- Spring Spring Boot 3.4.17, 3.5.14.1, 4.0.6.1
Is CVE-2026-40992 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4mo ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |
| GitHub | 3.1 | 5.0 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.boot:spring-boot-starter-mail | >=4.0.0, <4.0.7 >=3.5.0, <3.5.15 >=3.4.0, <=3.4.16 |
4.0.7 3.5.15 |
Affected products
- Spring Spring Boot
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
- Technology feeds
References
-
spring.io
/security/cve-2026-40992
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-40992
advisory
-
github.com
/spring-projects/spring-boot
package
Sources
- CVE List CVE-2026-40992
- GitHub Advisory GHSA-9wxp-w4px-32vh
- NVD CVE-2026-40992
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.