DEV Community

yutianle
yutianle

Posted on

Nhost title matches expose a role-resolved backend surface

Nhost title matches expose a role-resolved backend surface

Nhost combines authentication, GraphQL, storage, and serverless functions in a self-hostable backend platform. An exposed deployment is not one generic API. Requests resolve through a user identity, a selected role, and table or storage permissions. That means an exposure review needs to understand which role a request can assume before deciding what the endpoint can reach.

On November 20, 2026, ZoomEye returned 77 matches for title="Nhost" and zero for app="Nhost" with sub_type=all, page 1, and pagesize 1. The title field produces a small candidate set, while the application field does not identify a clean population. The count does not prove that every result is a live backend, and zero application matches are not evidence that no Nhost deployment exists.

Roles are part of the request path

Nhost documentation says each user has a default role and a list of allowed roles. A request uses one role to resolve GraphQL and storage permissions. The default role applies when no role is specified, and users can request only a role on their allowed list. The x-hasura-role header selects the role in GraphQL requests.

That model makes role assignment and permission rules the core of the authorization test. A public schema can expose a table name without exposing rows, but the effective result depends on the role's select, insert, update, and delete permissions. Storage has its own permission grid, including a public role for files intended to be readable without authentication.

Inventory the backend as a whole

Record the auth endpoint, GraphQL endpoint, storage endpoint, functions, dashboard, and custom domain. Identify the default role, allowed roles, anonymous sign-in setting, and whether public storage is enabled. Then inspect the permission rules for the tables and files that the application actually needs.

Test with a user who has the default role, a user with an additional allowed role, an anonymous request, and an expired token. Verify that a request for an unauthorized role fails and that a public object is limited to the intended path. Do not use administrative credentials for the external test.

Separate platform administration from application data

The dashboard and the public backend are different authority planes. A restricted backend can still be valuable to an attacker if it leaks user records or storage paths. A dashboard login can expose project configuration even when the data API is well scoped. Review both, but do not merge their counts into one vulnerability number.

Keep database migrations, function deployment, and secret configuration under a separate operator path. Rotate credentials used by functions and storage. Check whether an outbound function can reach an internal metadata service or a private network that the application should not access.

The 77 title matches provide a starting set for ownership checks. The useful evidence is the actual role response, the public storage rule, and the permission matrix. Nhost's design already gives the reviewer those concepts. The exposure count is only the invitation to examine them.

References

Top comments (0)