Skip to content
Applications

CVE-2026-1728

9.8
Critical
EPSS 0.30%Patch availableAug 6, 2026

Low-privilege tokens can access WSO2 Admin REST APIs, enabling admin takeover.

common questions

Is CVE-2026-1728 being exploited?

Not confirmed. CVE-2026-1728 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.30% probability of exploitation in the next 30 days.

How severe is CVE-2026-1728?

CVE-2026-1728 is rated Critical with a CVSS score of 9.8. 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-2026-1728?

Yes. A fix has been recorded for CVE-2026-1728. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-1728 affect?

CVE-2026-1728 affects WSO2 API Manager, WSO2 Identity Server, WSO2 Enterprise Integrator, WSO2 products (Admin REST APIs). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1728?

Revoke tokens, restrict token scopes and admin API access, audit logs, apply vendor patch when available.

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

executive summary
technical analysis
affected
WSO2 API ManagerWSO2 Identity ServerWSO2 Enterprise IntegratorWSO2 products (Admin REST APIs)
impact

Privilege escalation: attacker with a low-privilege account/token can invoke Admin REST APIs and achieve full administrative account takeover.

action required

Immediate action required

affected versions
WSO2 WSO2 API Control Plane
  • affected>= 4.5.0 and < 4.5.0.49
  • affected>= 4.6.0 and < 4.6.0.13
WSO2 WSO2 API Manager
  • affected< 4.0.0
  • affected>= 4.0.0 and < 4.0.0.384
  • affected>= 4.1.0 and < 4.1.0.248
  • affected>= 4.2.0 and < 4.2.0.188
  • affected>= 4.3.0 and < 4.3.0.99
  • affected>= 4.4.0 and < 4.4.0.63
  • affected>= 4.5.0 and < 4.5.0.48
  • affected>= 4.6.0 and < 4.6.0.12
WSO2 WSO2 Carbon API Manager Rest API Common Functions
  • affected>= 9.0.174 and < 9.0.174.550
  • affected>= 9.28.116 and < 9.28.116.404
  • affected>= 9.29.120 and < 9.29.120.221
  • affected>= 9.30.67 and < 9.30.67.146
  • affected>= 9.31.86 and < 9.31.86.130
  • affected>= 9.32.147 and < 9.32.147.26
vendor says fixed in>= 9.33.27 and <= *
WSO2 WSO2 Carbon API Manager Rest API Utility
  • affected>= 9.20.74 and < 9.20.74.392
vendor says fixed in>= 9.33.27 and <= *
WSO2 WSO2 Traffic Manager
  • affected>= 4.5.0 and < 4.5.0.47
  • affected>= 4.6.0 and < 4.6.0.12
WSO2 WSO2 Universal Gateway
  • affected>= 4.5.0 and < 4.5.0.48
  • affected>= 4.6.0 and < 4.6.0.12

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