When secondary user stores are configured, the implicit-association resolver incorrectly initializes from a secondary user store and bypasses the primary user store during search and uniqueness checks. This allows a subject to be associated with an unintended local account if the same lookup claim (e.g., username or email) exists in both the primary and a secondary store.

If duplicate claim values exist across user stores, this issue can lead to identity confusion due to incorrect implicit associations when using an external Identity Provider (IDP). Legitimate user accounts in the primary user store may fail to associate correctly with their corresponding external IDP accounts, potentially restricting access if the secondary account has fewer privileges. Deployments are not affected if no secondary user stores are configured, implicit association is disabled, or claim values are globally unique.

AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4493/

[{"vendor":"WSO2","product":"WSO2 Identity Server","defaultStatus":"unaffected","versions":[{"version":"7.0.0","lessThan":"7.0.0.132","versionType":"custom","status":"affected"},{"version":"7.1.0","lessThan":"7.1.0.40","versionType":"custom","status":"affected"}]},{"vendor":"WSO2","product":"Token Exchange Grant Type For OAuth","defaultStatus":"unknown","packageName":"org.wso2.carbon.extension.identity.oauth2.grantType.token.exchange:org.wso2.carbon.identity.oauth2.grant.token.exchange","versions":[{"version":"1.1.19","lessThanOrEqual":"*","versionType":"custom","status":"unaffected"}]}]