Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.0

Spring Boot's Mail Auto-Configuration Does Not Enable SSL Hostname Verification

CVE-2026-40992GHSA-9wxp-w4px-32vh

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-9wxp-w4px-32vh lists affected ranges: Maven org.springframework.boot:spring-boot-starter-mail >=4.0.0 =3.5.0 =3.4.0 <=3.4.16

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.0 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
EPSS
  • CVE-2026-40992: 0.12% estimated exploitation activity in the next 30 days; percentile 2.11 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9wxp-w4px-32vh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40992

Advisory: Spring Boot's Mail Auto-Configuration Does Not Enable SSL Hostname Verification
IDs: CVE-2026-40992, GHSA-9wxp-w4px-32vh
Record: https://patchnext.com/advisories/cve-2026-40992 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework.boot:spring-boot-starter-mail 4.0.7, 3.5.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.boot:spring-boot-starter-mail: affected >= 4.0.0, <= 4.0.6; >= 3.5.0, <= 3.5.14; >= 3.4.0, <= 3.4.16; fixed in 3.5.15, 4.0.7

## Suggested inspection (read-only)
- Maven org.springframework.boot:spring-boot-starter-mail: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework.boot:spring-boot-starter-mail.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9wxp-w4px-32vh (GitHub-reviewed advisory GHSA-9wxp-w4px-32vh lists affected ranges: Maven org.springframework.boot:spring-boot-starter-mail >=4.0.0 =3.5.0 =3.4.0 <=3.4.16)

Commands are suggestions: review each one before running it.

Loading voting…