Privilege Escalation via Token Endpoint in WSO2 API Manager (APIM 4.x/IS as Resident Key Manager)
Only deployments where WSO2 Identity Server is the Resident Key Manager with database sharing are affected, in WSO2 API Manager 4.1.0 through 4.6.0. The WSO2 Identity Server Key Manager Connector is fixed in 1.8.8.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.8
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.8.
- Exploitation0/40No signal
- Exposure20/25No login or user action needed, CISA rates it automatable · Data gap: Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity10/10CVSS 9.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 35 if advisories confirm default setups are exposed
CVE-2026-4052 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.8 (critical) and affects WSO2 API Manager, WSO2 API Control Plane and WSO2 Identity Server Key Manager Connector (apim-km-wso2is); fixed in 1.8.8.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.36% · 29th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 30/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 1.8.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
This issue affects WSO2 API Manager deployments that use WSO2 Identity Server as a Resident Key Manager with shared databases. In these setups, a self-registered user could obtain a token from the Identity Server token endpoint and use it to gain unauthorized access to API Manager's System REST APIs.
Read the original description
This issue only impacts deployments where WSO2 Identity Server is configured as a Resident Key Manager with database sharing. In such environments, a self-registered user may gain access to the System REST APIs of WSO2 API Manager by obtaining a token from the WSO2 Identity Server token endpoint.
What to do
Upgrade to a fixed version: 1.8.8.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0, 4.6.0
- WSO2 WSO2 API Control Plane
4.5.0, 4.6.0
- org.wso2.km.ext.wso2is:wso2is.key.manager.core
fixed in 1.8.8
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-4052
Is CVE-2026-4052 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A low-privileged user can invoke the System REST APIs of WSO2 API Manager, which can potentially lead to full administrative account takeover.Source: security.docs.wso2.com
Which versions are affected by CVE-2026-4052?
WSO2 API Manager: versions 4.1.0, 4.2.0, 4.3.0, 4.4.0, 4.5.0 and 1 more. WSO2 API Control Plane: versions 4.5.0, 4.6.0. org.wso2.km.ext.wso2is:wso2is.key.manager.core: before 1.8.8.Source: cve.now feed data
Am I affected, and how do I check?
The issue affects WSO2 API Manager 4.1.0 through 4.6.0 and WSO2 API Control Plane 4.5.0 and 4.6.0, and only where WSO2 Identity Server is configured as a Resident Key Manager with database sharing. To check, compare your API Manager version with the listed versions and review whether your Key Manager setup uses Identity Server as a Resident Key Manager with database sharing.Source: security.docs.wso2.com
How do I fix CVE-2026-4052?
Update the WSO2 Identity Server Key Manager Connector (apim-km-wso2is) to version 1.8.8 or later, which is the fixed version listed in the advisory facts.Source: security.docs.wso2.com