CVE-2026-72537

CVE-2026-72537 is a privilege escalation in Authentik's SCIM provisioning where a token constrained to a single identity source can silently hijack accounts outside its intended scope. The vulnerability stems from how Authentik processes incoming SCIM users: when a source-scoped token provides a username that already exists locally, the system adopts that entire account—including its privilege level, group memberships, and superuser status—without verifying the incoming identity actually belongs to the source the token is authorized to provision from. This is not a logic bug in the traditional sense. The token's 'source' parameter was implemented as organizational metadata—a useful tag for tracking where users came from—rather than as an authorization boundary. The SCIM ingest function searches for a matching local username and merges the incoming provisioner into that existing identity. The scoping constraint exists in the token but never gets enforced as a gate at provisioning time. The practical exploit is straightforward: obtain any source-scoped SCIM token, then provision a user with a superuser's existing username. The system hands over the account with all its elevated permissions. The CVSS 8.8 score accurately reflects the impact but may understate ease of exploitation in environments where SCIM tokens are accessible to compromised IdPs, supply chain compromises, or insider threats. Three questions demand answers in your environment. First, what is the realistic attack surface for SCIM token acquisition in your deployment? If tokens live inside a controlled IdP-to-Authentik pipeline with no exposure, the risk differs substantially from shared or third-party provisioning setups. Second, does your fix validate scope at ingest time, or does it prevent SCIM from adopting pre-existing local accounts entirely—treating provisioned users as distinct from local ones? The latter is more robust but may affect legitimate migration workflows. Third, current logging captures 'valid SCIM provisioning call' without emitting which user universe the token was authorized to touch. Without that signal, legitimate cross-source federation looks identical to in-scope privilege escalation. Audit your SCIM event schema and determine whether you can emit the token's authorized scope alongside the provisioning event—detection depends on it.

Reviewed through automated stages and approved by a human before publication.