CVE-2026-4052
Privilege Escalation via Token Endpoint in WSO2 API Manager (APIM 4.x/IS as Resident Key Manager)
No exploitation reported by the sources we read.
- Published2026-11-03
- WeaknessCWE-862
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-11-0308:02CVE publishedCNA
Observed activity
isMalicious corpus · updated 2026-11-03 09:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-4052?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-4052?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
Products declared by the CNA
As WSO2, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.
- WSO2 API Managerother versions: not affectedAffected
- = 4.1.0no fix statedcustom
- = 4.2.0no fix statedcustom
- = 4.3.0no fix statedcustom
- = 4.4.0no fix statedcustom
- = 4.5.0no fix statedcustom
- = 4.6.0no fix statedcustom
- WSO2 API Control Planeother versions: not affectedAffected
- = 4.5.0no fix statedcustom
- = 4.6.0no fix statedcustom
- WSO2 Identity Server Key Manager Connector (apim-km-wso2is)other versions: not affected
package org.wso2.km.ext.wso2is:wso2is.key.manager.core
Affected- < 1.8.8fixed in 1.8.8custom
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-03
Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-4052 yet.
Fix
No fix published by the sources we read yet. NVD record
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
- Metasploit modules
- none listed Metasploit Framework
Sources
Identifiers
- EUVD-2026-115721same flawENISA EUVD · LicenseRef-ENISA-legal-notice
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-11-03
- Last Modified
- 2026-11-03
- NVD status
- Received
Frequently asked questions
What is CVE-2026-4052?
Is CVE-2026-4052 actively exploited?
What is the CVSS score for CVE-2026-4052?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.