Authentication Bypass under Actuator Health Endpoints on Jersey

HIGH | NOVEMBER 19, 2026 | CVE-2026-59378

Description

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.

Affected Spring Products and Versions

Spring Boot:

  • 4.1.0 - 4.1.2
  • 4.0.0 - 4.0.9
  • 3.5.0 - 3.5.17
  • 3.0.0 - 3.4.18

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
4.1.2.1Enterprise Support Only
4.1.3OSS
4.0.9.1Enterprise Support Only
4.0.10OSS
3.5.18Enterprise Support Only
3.4.19Enterprise Support Only

Applications that cannot upgrade immediately can work around this issue by avoiding the path collision.

Avoid mapping application resources under the health path

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.

Credit

The issue was identified and responsibly reported by h1ei1.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all