Restate at 67 title matches and 20 application fingerprints: the Admin API is the control plane
Restate is a durable execution server for distributed applications. It exposes an HTTP ingress for application requests and an Admin API for deployments, invocations, subscriptions, and cluster operations. The Admin API is not a general application endpoint. A reachable admin listener can reveal service topology or let a caller change how the server interacts with deployments.
On November 18, 2026, ZoomEye returned 67 matches for title="Restate" and 20 for app="Restate" with sub_type=all, page 1, and page size 1. The title count may include documentation and unrelated uses of the word. The application count is a more specific product signal, but neither number proves administrative access or a vulnerable configuration.
The Restate 1.6 release notes describe separate Admin, HTTP Ingress, and message-fabric listeners. They also document Unix domain sockets for each service and a bind-ip default of 0.0.0.0 for TCP listeners. A deployment that starts the server without a network restriction can therefore make the Admin API reachable from any interface that can route to the host. The notes recommend Unix sockets in some environments and describe advertised addresses separately from bind addresses.
The two ports have different authority
The HTTP ingress is the path clients use to invoke services. The Admin API on the default port 9070 is the path operators use to register deployments, inspect invocations, and manage the runtime. A public ingress may be intentional. A public Admin API is a control-plane exposure unless an external authorization layer protects it.
Restate Cloud issues API keys with roles for its control plane. A self-hosted deployment may rely on network policy instead of application-level admin authentication. That design makes the bind address and the surrounding network policy part of the security boundary. A reverse proxy that exposes both ports under one hostname can accidentally publish the Admin API even when the ingress is the only intended endpoint.
Inventory every listener and its bind address. Identify every process using the Admin port and confirm whether it is bound to localhost, a private interface, a Unix socket, or all interfaces. Check the service's deployment address and the network policy that permits calls from service discovery or CI. A deployment may need the Admin API from a control pod, but that does not require internet reachability.
Service registration is privileged
The Admin API can register a deployment URL. A caller with that ability may point the server at a service the operator did not intend, alter a service definition, or cause the runtime to fetch an attacker-controlled address. The Restate issue tracker describes a proposed deployment-address allowlist for this reason, while noting that admin access is required and many deployments rely on network controls.
If the Admin API is exposed, review registered deployments, service names, invocation history, retry behavior, and network egress. Restrict the server's outbound network to the deployment endpoints it needs. Use a dedicated control network and require mutual authentication or network policy between the operator, the server, and the deployment.
The ingress also needs a separate review. A public ingress may accept requests to application handlers that perform privileged background work. Restate's durable execution model retries operations, so an authorization failure or a malicious request can be repeated across retries. Apply authentication at the application handler and at the network edge. Do not assume the runtime's retry policy is a security control.
From counts to a safe check
The 67 title and 20 application matches are useful for prioritisation, but they are not a map of owned systems. Start with known cluster inventories, Kubernetes services, Docker hosts, and operator-managed endpoints. For each owned instance, compare the running listener configuration with the expected design. Query only the service's public metadata or health endpoint if it is authorized.
For a production deployment, prefer Unix sockets or loopback for the Admin API, and expose only the ingress through a controlled load balancer. If the Admin API must be remote, require a private network, a strong identity layer, and an explicit authorization policy. Monitor for changes to deployments, unusual invocation patterns, and new outbound destinations.
The count is a reminder that operational tooling is often visible on the same networks as public applications. Restate's control-plane separation is a design strength only when the bind address and ingress policy enforce the separation.
Query evidence
title="Restate"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:43:36+08:00, count=67
app="Restate"
sub_type=all, page=1, pagesize=1, observed 2026-11-18T07:43:37+08:00, count=20
Top comments (0)