DEV Community

SorrelThorncroft
SorrelThorncroft

Posted on

Weaviate's anonymous-access option is the first boundary to check

Weaviate's anonymous-access option is the first boundary to check

Weaviate is a vector database used for semantic search and retrieval. Its public API can answer queries that reveal data in collections, including objects, properties, vectors, and tenant context. The choice between authenticated and anonymous access is therefore more consequential than the appearance of the landing page.

A count-only ZoomEye query on 2026-11-21 returned zero for app="Weaviate" and 62 for title="Weaviate". Both used sub_type=all, page 1, and page size 1. The title count is a lead, not a confirmed deployment count. The absence of an application fingerprint means an inventory cannot rely on app alone.

Weaviate documentation lists API key, OpenID Connect, and anonymous access as authentication options. It strongly discourages anonymous access outside development or evaluation. API keys and OIDC can be enabled together, and authorization can use RBAC, an admin list, or undifferentiated access depending on the deployment. Those controls define what a caller can do after the service knows who it is.

A deployment behind a reverse proxy still needs a Weaviate-side decision. If every request arrives through a single proxy identity with a broad key, the proxy must enforce per-user authorization before it forwards the request. If the proxy allows anonymous requests to pass, Weaviate may treat them as anonymous or reject them based on configuration. Test the complete path and record which layer made the decision.

Review the public API routes before the management features. Query and object retrieval can expose stored data. Class and schema endpoints can reveal collection names and property models. Backup, replication, and tenant operations can change availability or data scope. Use separate credentials for read-only queries, ingestion, and administration. Keep admin lists short and reviewed. Do not assume a hidden UI means an API is private.

Multi-tenancy adds another dimension. A cluster can host many tenants, and tenant names are often used in API paths. Authorization must check the caller against the tenant, not only against the collection. Test a denied tenant after a normal query and after a role change. Confirm that a missing tenant returns a safe response rather than leaking whether it exists.

The 62 title matches can include documentation pages, demos, and unrelated references. An owner should reconcile the observation with DNS and deployment records before investigating a host. External researchers should limit testing to a harmless request that identifies the service and should not enumerate objects or tenants.

Inventory the service, its auth mode, its authorization scheme, its public routes, and the credentials used by every client. The anonymous option is the first item because it changes who can make the first request. The remaining controls decide how far that request can go.

Exact query: title="Weaviate"

Open the normalized ZoomEye search

References

Top comments (0)