Quick answers
- Is CVE-2025-13166 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-13166 being exploited in the wild.
- How severe is CVE-2025-13166?
- Low severity, with a CVSS score of 3.7, published 15 September 2026.
- Which products and versions are affected?
- Wso2 Identity Server 7.1.0, 7.2.0.
- Is there a fix for CVE-2025-13166?
- A patch was published on 2026-05-03: Fixes available via GitHub PR #9434 and product updates Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-13166 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2025-13166?
- Check whether you run Wso2 Identity Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a user enumeration weakness in the SMS OTP authentication flow caused by improper error message handling. Attackers can send OTP initiation requests and analyze the response messages to infer whether a username is registered, with heightened success against accounts lacking a configured mobile number. The attack vector is network-based and requires no authentication or user interaction. A successful enumeration does not directly compromise user data or system functionality, but generates a list of valid usernames that facilitates follow-on attacks (brute force, social engineering). Fixes are available via GitHub pull request and product updates (Identity Server 7.2.0 update 2, 7.1.0 update 40).
Affected products
- WSO2 Identity Server 7.1.0, 7.2.0
Timeline
- 2026-05-03: disclosed
- 2026-05-03: patched: Fixes available via GitHub PR #9434 and product updates