Skip to content
Applications

CVE-2025-14561

CRITICAL
Critical
EPSS 0.39%Aug 7, 2026

Privilege escalation in Publisher REST APIs allows cross-tenant API metadata access/modification.

common questions

Is CVE-2025-14561 being exploited?

Not confirmed. CVE-2025-14561 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.

How severe is CVE-2025-14561?

CVE-2025-14561 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-14561?

Not known from our data. No patch reference has been recorded for CVE-2025-14561, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2025-14561 affect?

CVE-2025-14561 affects Multi-tenant Publisher REST APIs, API management platforms (publisher component). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-14561?

Restrict publisher privileges, enforce tenant isolation, apply vendor patch when available, monitor logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Multi-tenant Publisher REST APIsAPI management platforms (publisher component)
impact

A privileged user in one tenant can read/modify/expose API metadata in other tenants, enabling cross-tenant data/control compromise.

action required

Immediate action required

affected versions
WSO2 WSO2 API Control Plane
  • affected>= 4.5.0 and < 4.5.0.42
  • affected>= 4.6.0 and < 4.6.0.7
WSO2 WSO2 API Manager
  • affected>= 4.1.0 and < 4.1.0.242
  • affected>= 4.2.0 and < 4.2.0.182
  • affected>= 4.3.0 and < 4.3.0.93
  • affected>= 4.4.0 and < 4.4.0.57
  • affected>= 4.5.0 and < 4.5.0.41
  • affected>= 4.6.0 and < 4.6.0.6
WSO2 WSO2 Carbon API Management Implementation
  • affected>= 9.20.74 and < 9.20.74.388
  • affected>= 9.28.116 and < 9.28.116.395
  • affected>= 9.29.120 and < 9.29.120.213
  • affected>= 9.30.67 and < 9.30.67.135
  • affected>= 9.31.86 and < 9.31.86.108
  • affected>= 9.32.147 and < 9.32.147.5
vendor says fixed in>= 9.32.160 and <= *
WSO2 WSO2 Carbon API Manager Rest API Utility
  • affected>= 9.20.74 and < 9.20.74.388
  • affected>= 9.28.116 and < 9.28.116.395
  • affected>= 9.29.120 and < 9.29.120.213
  • affected>= 9.30.67 and < 9.30.67.135
  • affected>= 9.31.86 and < 9.31.86.108
  • affected>= 9.32.147 and < 9.32.147.5
vendor says fixed in>= 9.32.160 and <= *
WSO2 WSO2 Traffic Manager
  • affected>= 4.5.0 and < 4.5.0.40
  • affected>= 4.6.0 and < 4.6.0.6
WSO2 WSO2 Universal Gateway
  • affected>= 4.5.0 and < 4.5.0.40
  • affected>= 4.6.0 and < 4.6.0.6

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free