CVE-2025-14561: WSO2 Publisher REST APIs tenant isolation bypass in multi-tenant deployments

CVE-2025-14561 · Severity: critical · CVSS 9 · Published 2026-08-06

WSO2's API management products fail to properly isolate data between separate customer tenants in multi-tenant deployments. A privileged user in one tenant can exploit this to access and modify API metadata belonging to other tenants, potentially exposing sensitive configurations and allowing unauthorized API modifications across customer boundaries.

Technologies: Wso2 API Control Plane, Wso2 API Manager, Wso2 Traffic Manager, Wso2 Universal Gateway. Vendors: Wso2.

Quick answers

Is CVE-2025-14561 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-14561 being exploited in the wild.
How severe is CVE-2025-14561?
Critical severity, with a CVSS score of 9, published 6 August 2026.
Which products and versions are affected?
Wso2 API Control Plane 4.5.0, 4.6.0; Wso2 API Manager 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0, 4.6.0; Wso2 Traffic Manager 4.5.0, 4.6.0; Wso2 Universal Gateway 4.5.0, 4.6.0.
Is there a fix for CVE-2025-14561?
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-14561 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2025-14561?
Check whether you run Wso2 API Control Plane, Wso2 API Manager, Wso2 Traffic Manager or one of the others listed 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 cross-tenant access control bypass in the Publisher REST APIs, affecting only multi-tenant deployments. The root cause is insufficient tenant isolation enforcement in API access control logic. An authenticated user with sufficient privileges (e.g., API publisher role) in one tenant can invoke REST API endpoints that fail to validate tenant boundaries, allowing read and write operations on resources belonging to other tenants. No network-level authentication bypass is required—exploitation requires valid credentials and appropriate role permissions within the attacker's own tenant. Patches are available via GitHub PR #13546 and through WSO2 update subscriptions for all affected versions.

Affected products

  • WSO2 API Control Plane 4.5.0, 4.6.0
  • WSO2 API Manager 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0, 4.6.0
  • WSO2 Traffic Manager 4.5.0, 4.6.0
  • WSO2 Universal Gateway 4.5.0, 4.6.0

Timeline

  • 2026-01-26: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.