Spring Boot

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This CVE identity is linked to the Lifecycle record Spring Boot. Use that record for publisher support phases and retirement dates.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVE	Published	Affected versions	Fixed version information	Publisher evidence
CVE-2026-41001	11 Jun 2026	4.0.0 < 4.0.6.1; 3.5.0 < 3.5.14.1; 3.4.0 < 3.4.17; 3.3.0 < 3.3.20; 2.7.0 < 2.7.34	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40992	11 Jun 2026	4.0.0 < 4.0.6.1; 3.5.0 < 3.5.14.1; 3.4.0 < 3.4.17	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40977	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14; 3.4.0 < 3.4.16; 3.3.0 < 3.3.19; 2.7.0 < 2.7.33	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40976	27 Apr 2026	4.0.0 < 4.0.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40975	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14; 3.4.0 < 3.4.16; 3.3.0 < 3.3.19; 2.7.0 < 2.7.33	Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258	Update reference ↗
CVE-2026-40974	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14; 3.4.0 < 3.4.16; 3.3.0 < 3.3.19; 2.7.0 < 2.7.33	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40973	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14; 3.4.0 < 3.4.16; 3.3.0 < 3.3.19; 2.7.0 < 2.7.33	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40972	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14; 3.4.0 < 3.4.16; 3.3.0 < 3.3.19; 2.7.0 < 2.7.33	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40971	27 Apr 2026	4.0.0 < 4.0.6; 3.5.0 < 3.5.14	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-40970	27 Apr 2026	4.0.0 < 4.0.6	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2026-22731	19 Mar 2026	4.0 < 4.0.3; 3.5 < 3.5.11; 3.4 < 3.4.15	Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258	Update reference ↗
CVE-2025-22235	28 Apr 2025	2.7.x < 2.7.25; 3.1.x < 3.1.16; 3.2.x < 3.2.14; 3.3.x < 3.3.11; 3.4.x < 3.4.5	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2024-38807	23 Aug 2024	2.7.x < 2.7.22; 3.0.x < 3.0.17; 3.1.x < 3.1.13; 3.2.x < 3.2.9; 3.3.x < 3.3.3	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record
CVE-2023-34055	28 Nov 2023	2.7.0 < 2.7.18; 3.0.0 < 3.0.13; 3.1.0 < 3.1.6; older unsupported versions	Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258	Update reference ↗
CVE-2019-3797	6 May 2019	2.0 < v2.0.9.RELEASE; 1.5 < v1.5.20.RELEASE; 2.1 < v2.1.4.RELEASE	No fixed version is explicitly recorded in the structured CVE data.	Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.