/

CVE-2026-72534

Severity:

HIGH RISK

(8.8)

Improper Privilege Management (CWE-269) in Authentik SCIM

CVE-2026-72534

Deferred

Vulnerability type

Category:

Privilege Escalation

CWE:

CWE-269

Impact:

Superuser Privilege Escalation and Administrative Lockout

Severity:

HIGH RISK

(8.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A privilege management flaw in Authentik's SCIM provisioning workflow may allow a source-scoped provisioning token to obtain superuser privileges. The risk arises when a provisioned SCIM group matches an existing administrator group by name and the existing group's membership is replaced without validating source ownership.

Affected context

The vulnerability may affect Authentik deployments that:

  • Enable SCIM provisioning for a source
  • Issue provisioning tokens with permission to create or update groups
  • Have existing groups whose names can be matched by provisioned SCIM groups
  • Do not verify that the provisioning source is authorized to manage the matched target group

The impact depends on the permissions associated with the provisioning token and the role membership of the targeted group.

Exploit preconditions

  • Attack surface: SCIM group provisioning and group synchronization
  • Required access: A valid source-scoped SCIM provisioning token with group-management capability
  • Trigger point: Ingestion of a SCIM group whose name matches an existing administrator group
  • Why exploitation is possible: The ingest logic may adopt the existing group and replace its membership without enforcing source-scope ownership or authorization checks

Why this happens

The underlying issue is improper privilege management, mapped to CWE-269. The SCIM ingestion process treats a group name as sufficient to identify and manage an existing group, while failing to preserve the authorization boundary associated with the provisioning source. This insecure pattern allows a lower-scope provisioning principal to affect a higher-privilege group and its members.

Potential impact

  • A provisioning token may gain effective IdP superuser privileges
  • An attacker could modify privileged group membership
  • Existing administrators may be removed or locked out
  • Unauthorized access to administrative configuration and identity data could occur
  • The affected deployment could experience service disruption or account recovery complications

General mitigation guidance

Mitigation generally focuses on preserving authorization boundaries throughout SCIM synchronization.

Common defensive patterns include:

  • Binding managed groups to immutable source-specific identifiers rather than names alone
  • Enforcing source-scope and ownership checks before adopting or updating existing groups
  • Preventing source-scoped tokens from modifying privileged or locally managed groups
  • Applying least privilege to provisioning tokens and separating administrative groups from externally managed groups
  • Requiring explicit approval or policy controls for synchronization changes affecting privileged identities
  • Preserving recovery paths for administrators and monitoring changes to high-privilege group membership

How teams detect issues like this

Organizations can look for:

  • Static analysis and code review checks for group lookup by mutable names without ownership validation
  • Review signals showing external synchronization can update locally managed or privileged groups
  • Tests that verify source-scoped tokens cannot modify groups outside their authorized scope
  • Audit events involving SCIM changes to administrator, superuser, or other privileged groups
  • Alerts for unexpected membership replacement, administrator removal, or privilege changes following provisioning activity

Automated security review tools may help identify missing authorization checks and privilege-boundary violations.

Sources

SourceLink
github.comgithub.com/goauthentik/authentik

Frequently asked

questions

It may be exploitable through the SCIM provisioning interface when that interface is reachable and the attacker possesses an appropriately capable provisioning token.

The attacker generally needs a valid source-scoped SCIM provisioning token that can create or update groups. The token's effective permissions and deployment exposure determine the practical scope.

Enforce source ownership and authorization checks before any existing group is adopted or modified, and prevent externally scoped tokens from changing privileged groups unless explicitly authorized.

Use immutable resource identifiers, isolate externally managed groups from local administrative groups, apply least privilege to provisioning credentials, and continuously audit privileged membership changes.

Find out what's already
exploitable in your codebase.