Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring 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:
spring-boot-starter-jersey), rather than Spring MVC or WebFluxhealth 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=/
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.
Spring Boot:
| Fix version | Availability |
|---|---|
| 4.1.2.1 | Enterprise Support Only |
| 4.1.3 | OSS |
| 4.0.9.1 | Enterprise Support Only |
| 4.0.10 | OSS |
| 3.5.18 | Enterprise Support Only |
| 3.4.19 | Enterprise Support Only |
Applications that cannot upgrade immediately can work around this issue by avoiding the path collision.
Don't map a JAX-RS @Path resource under the same path used by the health endpoint or its additional paths
(for example /health/**, /livez, /readyz, or any Kubernetes probe path). This is not recommended regardless
of this issue, as it can interfere with other Actuator configuration.
The issue was identified and responsibly reported by h1ei1.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy