Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Allows Retrieval of Sensitive Data
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 3.1.0.357, 3.2.0.465, 3.2.1.84, 4.1.0.249, 4.2.0.189, and 19 more
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. An Event Publisher output adapter is configured with irrelevant properties
- 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
- 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? →
- 9/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? →
- Specific setups only
- Fix
- Fixed in 3.1.0.357, 3.2.0.465, 3.2.1.84, 4.1.0.249, 4.2.0.189, and 19 more
- 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: no
- Technical impact: partial
Summary
Several WSO2 products are affected by an issue where Event Publisher output adapters log configuration properties that are unrelated to their function, which can inadvertently record sensitive credentials or other confidential data. An attacker who can read the product's 'wso2carbon' log files could retrieve this exposed information and potentially use it to gain unauthorized access.
Read the original description
When an Event Publisher output adapter is configured with properties that are irrelevant to its function, the affected products log these irrelevant properties. This can inadvertently include sensitive user credentials or other confidential information depending on the nature of the misconfigured property. A malicious actor with access to the 'wso2carbon' log files could retrieve sensitive information logged by the system. This may potentially lead to unauthorized access if the logged data contains credentials or other critical secrets.
What to do
Check whether your setup matches what the bug needs.
An Event Publisher output adapter is configured with irrelevant propertiesUpgrade to a fixed version: 3.1.0.357, 3.2.0.465, 3.2.1.84, 4.1.0.249, 4.2.0.189, or one of 19 more.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 API Manager
From 3.1.0 · fixed in 3.1.0.357; From 3.2.0 · fixed in 3.2.0.465; From 3.2.1 · fixed in 3.2.1.84; From 4.1.0 · fixed in 4.1.0.249; From 4.2.0 · fixed in 4.2.0.189; From 4.3.0 · fixed in 4.3.0.100; From 4.4.0 · fixed in 4.4.0.64; From 4.5.0 · fixed in 4.5.0.49; From 4.6.0 · fixed in 4.6.0.13
- WSO2 WSO2 Traffic Manager
From 4.5.0 · fixed in 4.5.0.48; From 4.6.0 · fixed in 4.6.0.13
- WSO2 WSO2 API Control Plane
From 4.5.0 · fixed in 4.5.0.50; From 4.6.0 · fixed in 4.6.0.14
- WSO2 WSO2 Universal Gateway
From 4.5.0 · fixed in 4.5.0.49; From 4.6.0 · fixed in 4.6.0.13
- WSO2 WSO2 Identity Server
From 5.10.0 · fixed in 5.10.0.386; From 5.11.0 · fixed in 5.11.0.433; From 6.0.0 · fixed in 6.0.0.260; From 6.1.0 · fixed in 6.1.0.261; From 7.0.0 · fixed in 7.0.0.139; From 7.1.0 · fixed in 7.1.0.47; From 7.2.0 · fixed in 7.2.0.8
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.377
- WSO2 WSO2 Open Banking IAM
From 2.0.0 · fixed in 2.0.0.426
- WSO2 WSO2 Open Banking AM
From 2.0.0 · fixed in 2.0.0.406
- org.wso2.carbon.analytics-common:org.wso2.carbon.event.publisher.core
fixed in 5.2.65; From 5.3.0 · fixed in 5.3.28
Evidence 1
- Advisory
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-18800
What does this mean?
When an Event Publisher output adapter is configured with irrelevant properties, the affected WSO2 products write those properties to the 'wso2carbon' log files. Anyone who can read those logs could then see sensitive information the system recorded there, which could lead to unauthorized access.Source: security.docs.wso2.com
Am I affected, and how do I check?
The advisory lists WSO2 API Manager, Traffic Manager, API Control Plane, Universal Gateway, Identity Server, Identity Server as Key Manager, Open Banking IAM and AM, and Carbon Event Publisher Core, each across several version ranges. The issue needs an Event Publisher output adapter configured with irrelevant properties, so check the product version and whether any such adapter is set up in the Event Publisher configuration.Source: security.docs.wso2.com
What should I do about it?
Upgrade to the fixed release for your product line, such as API Manager 4.6.0.13, Identity Server 7.2.0.8, or Carbon Event Publisher Core 5.3.28 for the 5.3 line. Check the advisory's product list for the exact fixed build that matches your version.Source: security.docs.wso2.com
Is it 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