Account impersonation via Silent JIT username collision
Published Feb 24, 2026 · Updated Feb 24, 2026
Authentication bypass in WSO2 API Manager 4.2.0 and Identity Server 6.0.0 and 6.1.0 allows remote attackers to impersonate local users. Silent JIT provisioning associates a new federated identity with an existing local account when both identities supply the same username, replacing the local user's information. Exploitation requires Silent JIT, a fresh valid federated account, knowledge of a local username, and a matching username at the federated provider.
Summary
What happened
Authentication bypass in WSO2 API Manager 4.2.0 and Identity Server 6.0.0 and 6.1.0 allows remote attackers to impersonate local users. Silent JIT provisioning associates a new federated identity with an existing local account when both identities supply the same username, replacing the local user's information. Exploitation requires Silent JIT, a fresh valid federated account, knowledge of a local username, and a matching username at the federated provider.
The record
- CVE
- CVE-2024-1524
- Published
- Feb 24, 2026
- Updated
- Feb 24, 2026
- Vendor
- WSO2
- Product
- WSO2 Identity Server
- Classifications
- CWE-290, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2026CVE publishedPublication date reported by the CVE source.
- Feb 24, 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=6.0.0 <6.0.0.171
- Affected versionversion=6.1.0 <6.1.0.128
What conditions does exploitation require?
What is affected?
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.
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