Spring Boot
Approved changes feed: RSS · Atom
cpe:2.3:a:spring:spring_boot:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Spring (4c7a31af-cbd7-516f-b1ce-2d5f574797bc) |
|---|---|
| Product | Spring Boot (d3569fb4-52eb-597d-9b87-97054561f4f0) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-41001 |
vulnerable | 2026-07-29 00:49:30.837079 |
Predictable Temp Directory in Artemis Auto-configuration
MEDIUM (5.3)
Spring Boot's ArtemisEmbeddedConfigurationFactory uses a fixed, static path for the embedded Artemis message broker's data directory when no explicit path is configured. A local attacker on the same host can pre-create this predictable directory or place a symlink before the application starts.
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; 3.3.0 through 3.3.19; 2.7.0 through 2.7.33.
Published: 2026-06-11T05:04:28.663Z
Updated: 2026-06-23T19:54:20.854Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40992 |
vulnerable | 2026-07-29 00:49:30.832360 |
Mail Auto-Configuration Does Not Enable SSL Hostname Verification
MEDIUM (5)
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: 2026-06-11T05:03:53.539Z
Updated: 2026-06-23T19:46:36.493Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40977 |
vulnerable | 2026-06-08 08:03:14.525166 |
Details available
MEDIUM (4.7)
When an application is configured to use `ApplicationPidFileWriter`, a local attacker with write access to the PID file's location can corrupt one file on the host each time the application is started.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); PID file / symlink behavior (`ApplicationPidFileWriter`). Versions that are no longer supported are also affected per vendor advisory.
Published: 2026-04-27T23:36:06.654Z
Updated: 2026-04-28T14:34:36.220Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40976 |
vulnerable | 2026-06-08 08:03:14.524638 |
Details available
CRITICAL (9.1)
In certain circumstances, Spring Boot's default web security is ineffective allowing unauthorized access to all endpoints. For an application to be vulnerable, it must: be a servlet-based web application; have no Spring Security configuration of its own and rely on the default web security filter chain; depend on spring-boot-actuator-autoconfigure; not depend on spring-boot-health. If any of the above does not apply, the application is not vulnerable.
Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.
Published: 2026-04-27T23:34:51.422Z
Updated: 2026-07-15T01:00:17.230Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40975 |
vulnerable | 2026-06-08 08:03:14.524146 |
Details available
MEDIUM (4.8)
Values produced by ${random.value} are not suitable for use as secrets. ${random.uuid} is not affected. ${random.int} and ${random.long} should never be used for secrets as they are numeric values with a predictable range.
Affected: Spring Boot 4.0.0–4.0.5 (fix 4.0.6), 3.5.0–3.5.13 (fix 3.5.14), 3.4.0–3.4.15 (fix 3.4.16), 3.3.0–3.3.18 (fix 3.3.19), 2.7.0–2.7.32 (fix 2.7.33); random value property source / weak PRNG for secrets. Versions that are no longer supported are also affected per vendor advisory.
Published: 2026-04-27T23:32:58.596Z
Updated: 2026-07-15T01:00:19.147Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40974 |
vulnerable | 2026-06-08 08:03:14.523640 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40973 |
vulnerable | 2026-06-08 08:03:14.522969 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40972 |
vulnerable | 2026-06-08 08:03:14.522478 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40971 |
vulnerable | 2026-06-08 08:03:14.521927 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-40970 |
vulnerable | 2026-06-08 08:03:14.516355 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22731 |
vulnerable | 2026-06-08 07:51:13.732980 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-22235 |
vulnerable | 2026-06-08 07:10:52.515256 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-38807 |
vulnerable | 2026-06-08 06:41:48.139605 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34055 |
vulnerable | 2026-06-08 06:06:24.331593 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-3797 |
vulnerable | 2026-06-08 05:13:56.008373 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.