CVE-2025-52553: authentik has Insufficient Session verification for Remote Access Control endpoint access
authentik is an open-source identity provider. After authorizing access to a RAC endpoint, authentik creates a token which is used for a single connection and is sent to the client in the URL. This token is intended to only be valid for the session of the user who authorized the connection, however this check is missing in versions prior to 2025.6.3 and 2025.4.3. When, for example, using RAC during a screenshare, a malicious user could access the same session by copying the URL from the shown browser. authentik 2025.4.3 and 2025.6.3 fix this issue. As a workaround, it is recommended to decrease the duration a token is valid for (in the RAC Provider settings, set Connection expiry to minutes=5 for example). The maintainers of authentik also recommend enabling the option Delete authorization on disconnect.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-52553?
CVE-2025-52553 has been classified with a moderate severity level due to potential risks in token management.
How do I fix CVE-2025-52553?
To fix CVE-2025-52553, upgrade authentik to version 2025.4.4 or later.
What systems are affected by CVE-2025-52553?
CVE-2025-52553 affects authentik versions earlier than 2025.4.4 and later than 2025.6.3.
What does CVE-2025-52553 involve?
CVE-2025-52553 involves issues with token validation for sessions in authentik, which may lead to unauthorized access.
Is there a workaround for CVE-2025-52553?
Currently, there are no official workarounds for CVE-2025-52553; upgrading is recommended.