Summary
A broken access control vulnerability in authentik's Remote Access Control endpoint API allows any authenticated user to view all configured remote endpoints, including connection settings that may contain stored credentials. An attacker may also open connections to endpoints assigned to applications they are not authorized to access.
Affected context
The issue occurs in deployments using authentik's enterprise Remote Access Control provider. The endpoint listing may return resources without applying endpoint or application-level authorization, while the connection flow may fail to verify that the selected endpoint belongs to the application that initiated the request. Deployments that do not use this provider are not affected.
Exploit preconditions
- Attack surface: Authenticated Remote Access Control API and connection flow
- Required access: Any valid authentik user account
- Trigger point: Listing configured endpoints or initiating a remote connection
- Why exploitation is possible: Authorization checks are not consistently applied to endpoint enumeration and endpoint-to-application ownership validation
Why this happens
The vulnerability results from an authorization design failure in which resource-level and application-level access controls are not enforced at every API and connection-flow boundary. Endpoint data is exposed based on authentication alone, and the connection process does not reliably confirm that the requested endpoint is authorized for the originating application. This maps primarily to CWE-639, Authorization Bypass Through User-Controlled Key, and is also related to CWE-863, Incorrect Authorization.
Potential impact
- An attacker may discover hosts and connection details for protected endpoints.
- Stored credentials for managed RDP, SSH, or VNC targets could be disclosed.
- An attacker could open interactive sessions to systems assigned to other applications.
- Compromised remote systems could enable further lateral movement or data access.
General mitigation guidance
Mitigation generally focuses on enforcing authorization consistently at both
resource enumeration and connection execution boundaries.
Common defensive patterns include:
- Applying server-side endpoint and application authorization checks to every response and action.
- Verifying endpoint ownership and permitted application context immediately before connection establishment.
- Returning only fields required by the requesting user and excluding stored secrets from general listing responses.
- Separating credential retrieval from endpoint metadata and protecting it with least-privilege access.
- Using deny-by-default policies and explicit tenant, group, and application scope checks.
- Auditing existing endpoint assignments and rotating credentials if unauthorized disclosure may have occurred.
How teams detect issues like this
Organizations can look for this class of issue through:
- Authorization tests confirming that users cannot enumerate endpoints outside their assigned applications.
- Integration tests covering both endpoint listing and connection establishment with mismatched application contexts.
- Static and dynamic analysis for resource queries that use authentication without authorization predicates.
- Code review checks for missing ownership, tenant, role, or application-scope validation.
- API gateway or policy rules that restrict sensitive endpoint metadata and credential-bearing fields.
- Monitoring for unusual endpoint enumeration, cross-application connection attempts, and access to remote targets outside normal user scope.

