Account takeover via unscoped SCIM user adoption
Published Aug 11, 2026 · Updated Aug 11, 2026
Privilege escalation in authentik through 2026.5.6 allows remote authenticated users to take over any account through SCIM provisioning. The SCIM user ingest path matches a provisioned username to an existing local account and adopts that account without enforcing the token's source scope. A source-scoped SCIM provisioning token is sufficient to rewrite or delete accounts, including superusers, but the flaw does not remove the need for that credential.
Summary
What happened
Privilege escalation in authentik through 2026.5.6 allows remote authenticated users to take over any account through SCIM provisioning. The SCIM user ingest path matches a provisioned username to an existing local account and adopts that account without enforcing the token's source scope. A source-scoped SCIM provisioning token is sufficient to rewrite or delete accounts, including superusers, but the flaw does not remove the need for that credential.
The record
- CVE
- CVE-2026-72537
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Authentik Security
- Product
- authentik
- Classifications
- T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2026.5.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo