Security fixes are released for the latest patch of each supported line.

Please do not open a public issue for a security problem.

Report it through GitHub's private vulnerability reporting:

1. Go to the Security tab.
2. Describe the issue, the affected version, and how to reproduce it.

You can expect an acknowledgement within 5 working days and an assessment within 15 working days. If a fix is warranted, a patched release and a GitHub Security Advisory are published together, crediting you unless you ask otherwise.

This starter reads annotation metadata from the beans in your application context and exposes it over HTTP. It never executes agents, never reads the blackboard, and never touches model credentials.

What it does expose is a description of your application's internals: agent class names, method names, goal descriptions, prompts' example strings, and condition names. Treat those endpoints as privileged.

Both switches are off by default, and neither endpoint adds any authentication of its own. In an environment where the application is reachable by untrusted clients, secure them like any other management surface — for example with Spring Security:

import org.springframework.boot.security.autoconfigure.actuate.web.servlet.EndpointRequest;
import org.springframework.security.web.servlet.util.matcher.PathPatternRequestMatcher;
import org.springframework.security.web.util.matcher.OrRequestMatcher;

@Bean
SecurityFilterChain visualizerSecurity(HttpSecurity http) throws Exception {
    return http
        .securityMatcher(new OrRequestMatcher(
            PathPatternRequestMatcher.withDefaults().matcher("/embabel-workflows/**"),
            EndpointRequest.to("embabel")))
        .authorizeHttpRequests(auth -> auth.anyRequest().hasRole("ADMIN"))
        .httpBasic(Customizer.withDefaults())
        .build();
}

Two details are easy to get wrong. All three endpoints publish the same catalog, so matching only the UI path leaves /actuator/embabel serving it unprotected — hence both matchers above. And the path pattern has to follow embabel.workflow.visualizer.base-path: change that property and this matcher stops covering anything.

EndpointRequest moved in Spring Boot 4. On the 0.3.x line (Boot 3) it is org.springframework.boot.actuate.autoconfigure.security.servlet.EndpointRequest instead.

The bundled UI is a single self-contained page: it loads no third-party scripts, fonts, or styles, and makes exactly one request — to its own API — so it adds no external origins to your application.