Skip to content
VulniPulse
Medium6.5Red Hat Linux

Medium [CVE-2026-18710] Credential disclosure via cleartext logging during client initialization

This medium-severity Red Hat Linux advisory covers CVE-2026-18710 affecting Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Debezium 3, Red Hat build of Quarkus.

CVE-2026-18710 Published Aug 11, 2026Updated by vendor Aug 11, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in org.mongodb/mongodb-driver. During routine client initialization, sensitive configuration information, including credentials for outbound network connectivity, is written to application log output in cleartext.

A local attacker with the ability to read the affected application's logs or downstream log-aggregation storage could recover these credentials. This allows them to reuse the credentials to authenticate to the associated network infrastructure, leading to information disclosure.

This vulnerability has Moderate impact. A flaw in MongoDB driver components used by Red Hat products can lead to sensitive credential disclosure.

An attacker with local access to these logs could recover and reuse the credentials, compromising confidentiality. Red Hat severity: Moderate — CVSS 6.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N).

Weakness: CWE-312. Affected Red Hat products: Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Debezium 3; Red Hat build of Quarkus.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, ensure that access to application logs and any downstream log aggregation storage is strictly controlled. Implement robust access control mechanisms to prevent unauthorized parties from reading log output, as this is where sensitive credentials may be exposed in cleartext during MongoDB driver client initialization. Regularly review and audit log access permissions.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.