Medium Cryptography

CVE-2026-40992 — Mail Auto-Configuration Does Not Enable SSL Hostname Verification

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.

Published Jun 11, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: vmware

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.19%

ahead of 8% of scored CVEs · Oct 14, 2026

Affects

Spring

Spring Boot

CVSS base

5.0

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Spring Spring Boot, Vmware Spring Boot).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Spring	Spring Boot	≥ 4.0.0 and < 4.0.6.1≥ 3.5.0 and < 3.5.14.1≥ 3.4.0 and < 3.4.17	Vulnerable	CVE Program (cve.org) e CISA ADP
Vmware	Spring Boot	≥ 3.4.0 and < 3.4.17≥ 3.5.0 and < 3.5.14.1≥ 4.0.0 and < 4.0.6.1	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Adjacent

Attack complexity

High

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.0	CVSS 3.1	Medium	1.6	3.4	security@vmware.com via NIST National Vulnerability Database
5.0	CVSS 3.1	Medium	—	—	vmware via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L (score shown at the top: security@vmware.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-295 · Improper Certificate Validation

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.19%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Check TLS negotiations and unexpected certificates in the component’s traffic.

network IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · spring/spring boot
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 5.0
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Analyzed
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jun 11, 2026 · vmware

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

spring.io/security/cve-2026-40992
Vendor Advisory, NIST National Vulnerability Database

Elsewhere on this site

Spring
every CVE for this vendor

Cryptography
same class

CWE-295
other pages naming this weakness

Related CVEs (same products)

Medium CVE-2026-41001 Predictable Temp Directory in Artemis Auto-configuration Jun 11, 2026
High CVE-2026-40972 An attacker on the same network as the remote application may be able to utilize a… Apr 27, 2026
High CVE-2026-40973 A local attacker on the same host as the application may be able to take control of the… Apr 27, 2026
Critical CVE-2026-40974 Improper Certificate Validation in Vmware Spring Boot Apr 27, 2026
High CVE-2026-40975 Use of Insufficiently Random Values in Vmware Spring Boot Apr 27, 2026
Critical CVE-2026-40976 Missing Authorization in Vmware Spring Boot Apr 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-40992 is "Mail Auto-Configuration Does Not Enable SSL Hostname Verification", rated Medium. It affects Spring Boot (Spring); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.0 describes technical severity. EPSS 0.19% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.