Quick answers
- Is CVE-2025-0326 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-0326 being exploited in the wild.
- How severe is CVE-2025-0326?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- WSO2 API Platform.
- Is there a fix for CVE-2025-0326?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-0326 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-0326?
- Check whether you run Wso2 API Platform. 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 stems from incomplete token lifecycle management during sensitive account operations (password reset, role change, sub-organization disablement) affecting sub-organization users. Previously issued access tokens are not invalidated when the user's access context is modified or revoked administratively, allowing token reuse by attackers who have obtained them. Exploitation requires the access token to have been previously exposed and remains limited to sub-organization user contexts.
Affected products
- WSO2 API Platform
Timeline
- 2026-10-21: disclosed