Authentication bypass in goauthentik authentik Source stage

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-49448?

CVE-2026-49448 is a vulnerability classified as Improper Authentication, affecting authentik (affected versions: < 2025.12.6, < 2026.2.4, and other affected versions). This vulnerability is rated Critical, with a CVSS score of 9.8. Public exploit code or evidence is available for this vulnerability, but that does not confirm exploitation in the wild.

Overview

Original source data

authentik is an open-source identity provider. Prior to versions 2025.12.6, 2026.2.4, and 2026.5.1, the Source stage can be bypassed by sending an empty POST. This issue has been patched in versions 2025.12.6, 2026.2.4, and 2026.5.1.

Affected products and scope

The following goauthentik authentik branches are confirmed affected:

  • 2025 branch: versions <=2025.12.5 are affected; the fix is 2025.12.6.
  • 2026.2 branch: versions <=2026.2.3 are affected; the fix is 2026.2.4.
  • 2026.5 branch: versions <=2026.5.0 are affected; the fix is 2026.5.1.

Branches or deployment forms not listed here should not be assumed safe or affected without additional vendor confirmation.

Technical details

This is an improper authentication condition in the Source stage component of goauthentik authentik. When a Source stage is bound to a flow, the source exposes a ui_login_button, and an attacker can reach that stage, an empty POST can cause the stage to be bypassed, effectively skipping authentication at that source. The record indicates that the attack is network reachable and requires neither prior privileges nor user interaction. The implementation detail that causes the failure, the exact endpoint, and the state handling after the stage is bypassed are not disclosed in the available evidence.

Exploitability

An attacker must be able to reach a Source stage in a flow that meets the documented configuration conditions. The record flags a public exploit, but the supplied evidence contains no exploit code, payload, exact endpoint, or reproduction instructions. The record does not confirm active exploitation, a specific campaign, or specific victims. No prior authentication or user interaction is required according to the supplied information.

Technical impact

The flaw allows a request with no content to bypass Source stage, and therefore skip authentication at the source under the documented configuration conditions. The technical result may be completion of a flow without the expected identity checks. This can affect the confidentiality and integrity of resources behind the flow and weaken access control in the identity service. The privileges obtained after bypass are not established and depend on the flow, source, and integrated application configuration. The record does not provide evidence of a specific administrative privilege, a specific intrusion, or an incident that occurred.

Business impact

  • An unauthenticated user may bypass source authentication in affected flows.
  • This could enable unauthorized access to applications, data, or functions protected by the affected flow.
  • The practical consequence depends on the services attached to the flow, the permissions granted after completion, and the source configuration.
  • Organizations should prioritize updating authentik deployments with the relevant flow configuration and review exposed flows.
  • The record provides no evidence of a specific data disclosure, data modification, or service outage.

Remediation

  1. Upgrade goauthentik authentik to the fixed release for the deployed branch: 2025.12.6, 2026.2.4, or 2026.5.1.
  2. Before and after upgrading, inventory flows that use Source stage and sources that expose ui_login_button, then verify the authentication behavior of those flows.
  3. If an immediate upgrade is not possible, identify the routes or flows that expose Source stage and apply deployment-appropriate access controls. Treat this only as a temporary risk-reduction measure, not as a replacement for the fix.
  4. The available evidence does not document a vendor-confirmed workaround. For branches outside the listed scope, verify status with the vendor before concluding that a fix applies.

Detection

  • Inventory running authentik versions and identify systems that use Source stage.
  • Review configuration for flows bound to Source stage, especially sources that expose ui_login_button.
  • If the application records requests to Source stage routes, look for POST requests with no content and correlate them with successful flow completions.
  • If application logs record source transitions, review completed flows that lack a corresponding source-authentication event. This is a precautionary check based on the documented mechanism, not a vendor-confirmed IOC.
  • Do not treat the absence of matching log entries as proof that a system is safe.
Sources (9)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.