# CVE-2026-0637: Sensitive Information Disclosure via Event Publisher Logging in Multiple WSO2 Products

> Attackers with log access can retrieve sensitive credentials due to unsanitized logging of misconfigured Event Publisher properties in WSO2 products.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-q9jj-jm6w-fpgf

## What is CVE-2026-0637?

CVE-2026-0637 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

When an Event Publisher output adapter is configured with irrelevant properties, the affected products log these properties. This logging occurs without sufficient validation or sanitization of the property values.

A malicious actor with access to the 'wso2carbon' log files could retrieve sensitive information, such as user credentials or other confidential data, that was inadvertently logged due to misconfiguration, potentially leading to unauthorized access.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-0637?

It affects 8 products.


Products: Wso2 Api Control Plane, Wso2 Api Manager, Wso2 Identity Server, Wso2 Identity Server as Key Manager, Wso2 Open Banking Am, Wso2 Open Banking Iam, Wso2 Traffic Manager, Wso2 Universal Gateway.

## How do I fix CVE-2026-0637?

No fix has been published for CVE-2026-0637 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0637 being exploited?

There is no known exploitation of CVE-2026-0637 in the wild and no public exploit code.

## Other vulnerabilities in Wso2 Api Manager

- [CVE-2026-5430](https://insights.sbomify.com/CVE-2026-5430/): WSO2 Multiple Products Path Traversal Vulnerability (critical 10.0, exploited in the wild)
- [CVE-2026-1728](https://insights.sbomify.com/CVE-2026-1728/): Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover (critical 9.8)
- [CVE-2025-9312](https://insights.sbomify.com/CVE-2025-9312/): Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products (critical 9.8)
- [CVE-2025-10611](https://insights.sbomify.com/CVE-2025-10611/): Potential Broken Access Control in Multiple WSO2 Products via System REST APIs (critical 9.8)
- [CVE-2025-9152](https://insights.sbomify.com/CVE-2025-9152/): Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0637 and fix it if it is affected.

What it is: CVE-2026-0637 is a medium-severity vulnerability in Wso2 Api Manager, published on 6 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0637 in the wild and no public exploit code.

Affected product: Wso2 Api Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0637/ (Markdown: https://insights.sbomify.com/CVE-2026-0637/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0637
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0637
- OSV: https://osv.dev/vulnerability/CVE-2026-0637

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0637/
Summaries are generated and may contain mistakes; the official description above is the record.