CVE Watchtower

CVE-2026-59378Spring Boot

Spring

Vulnerability Summary

Authentication Bypass under Actuator Health Endpoints on Jersey. Spring Boot applications with Actuator can be vulnerable to an "Authentication Bypass" vulnerability when an application resource that requires authentication is mapped under the same path used by the health endpoint. More precisely, an application can be vulnerable when all the following are true: the application is a Jersey-based web application (spring-boot-starter-jersey), rather than Spring MVC or WebFlux the application has the Actuator dependency on the classpath the application has the Spring Security dependency on the classpath, relying on the default security configuration the health endpoint is exposed on a path also used by an application-provided resource, either through an additional health path (for example management.endpoint.health.probes.add-additional-paths=true, or a health group's additional-path), or through management.endpoints.web.base-path=/ the application contributes a JAX-RS resource at that same path which requires authentication Note that mapping application endpoints under infrastructure endpoints like Actuator's is not recommended by the Spring team, and doing so is likely to interfere with other configurations and cause behavior problems. While the severity for this advisory is high, we expect this setup to rarely occur in production. This CVE is related to CVE-2026-22731 and CVE-2026-22733, which addressed similar issues.
Severity Level
HIGH(8.2)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 8.2 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Spring Boot 4.1.0 through 4.1.2
  • Spring Boot 4.0.0 through 4.0.9
  • Spring Boot 3.5.0 through 3.5.17
  • Spring Boot 3.0.0 through 3.4.18
Patched Versions
  • Spring Boot 4.1.3 (open source)
  • Spring Boot 4.0.10 (open source)
  • Spring Boot 4.1.2.1 (commercial support only)
  • Spring Boot 4.0.9.1 (commercial support only)
  • Spring Boot 3.5.18 (commercial support only)
  • Spring Boot 3.4.19 (commercial support only)

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Spring Boot and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring Boot CVEsYou are reading CVE-2026-59378. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Boot CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC