CVE-2026-18800: Medium severity vulnerability

Published Nov 2, 2026
·
Updated

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.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Remove irrelevant properties from the Event Publisher output adapter configuration so they are not logged.

    Event Publisher output adapter configured properties = only properties relevant to the adapter's function

Event History

Nov 2, 2026
CVE Published
via NVD·10:17 AM
Data Sourced
via NVD·10:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to this issue?

Deployments are exposed when an Event Publisher output adapter is configured with properties that are irrelevant to its function and those properties contain credentials or other confidential values. Exploitation also requires access to the wso2carbon log files.

2

What does an attacker need to do to obtain sensitive information?

The attacker needs access to the wso2carbon logs and must locate values logged from irrelevant Event Publisher output-adapter properties. The impact depends on whether the misconfigured properties contained credentials or other critical secrets.

3

What can be done if patching is not immediately possible?

Review Event Publisher output-adapter configurations and remove irrelevant properties, especially any that contain credentials or confidential information. Restrict access to wso2carbon log files to prevent unauthorized users from reading previously logged values.

4

How can teams determine whether they may already be affected?

Inspect Event Publisher output-adapter configurations for properties unrelated to the adapter's function, then review wso2carbon logs for sensitive values that may have been recorded. If credentials or secrets appear in the logs, treat them as exposed.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203