Live › vulnerability › CVE-2025-10149
Go to dashboardWhen a local user and a federated user share a username, the SCIM 2.0 and SCIM 1.1 endpoints fail to check that a federated user is allowed to touch the local account. An authenticated federated user can therefore run arbitrary operations on local accounts, which can lead to account takeover.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Deployments that accept federated logins and also expose the SCIM endpoint while holding local user accounts that share usernames with federated identities. The sources say deployments that do not support user self-registration are considered medium severity, so self-registration status matters for risk. Deployments without federation or without SCIM enabled are not described as exposed.
No product ranges from the sources yet.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The SCIM endpoint does not sufficiently validate authorization for federated users when performing operations against the local user store. This occurs when a local and a federated user share the same username, allowing a federated user to perform actions intended for a local user, including arbitrary operations.
A malicious actor authenticated as a federated user may perform arbitrary operations on local user accounts via the SCIM 2.0 or SCIM 1.1 endpoints when local and federated users share the same username. This could lead to user account takeover. Deployments that do not support user self-registration are considered medium severity.
This page as .md · .json · in your agent: get_signal("CVE-2025-10149")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.