When an Event Publisher output adapter is configured with properties that are irrelevant to its function, the affected
Source GCVE Database
Not known to be exploited · CVSS 4.4 Medium · fixed in 4.6.0.13 : update WSO2 API Manager when convenient.
Data as of 2 Nov 2026, 13:31 UTC
Thin evidence
One scorer or none| CNA (WSO2) | CVSS 3.1 | 4.4 |
|---|
- Patch
- Available – fixed in 4.6.0.13, 4.5.0.49, 4.4.0.64 +23
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
| WSO2WSO2 API Manager | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Mitigation involves ensuring that Event Publisher output adapters are configured correctly to avoid logging irrelevant or sensitive properties. Restrict access to 'wso2carbon' log files to trusted personnel only to prevent unauthorized retrieval of sensitive information.
Description
This vulnerability involves the logging of irrelevant properties by an Event Publisher output adapter, which can include sensitive user credentials or confidential information if misconfigured. An attacker with access to the 'wso2carbon' log files could extract this sensitive data, potentially leading to unauthorized access. The issue is due to improper handling of configuration properties in logging.