MongoDB Driver may publish events containing authentication-related dataGHSA-vxvm-qww3-2fh7
MEDIUMFix: mongodb/mongo-php-driver#1235GHSA-vxvm-qww3-2fh7 is a medium-severity (CVSS 4.2) Information Exposure vulnerability in mongodb. A fix is available for mongodb — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-vxvm-qww3-2fh7.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
mongodbnpmDescription
Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.
Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).
This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | mongodb | ≥ 3.6.0&&< 3.6.10 | 3.6.10npm install mongodb@3.6.10 |
| 📦npm | mongodb | ≥ 4.0.0&&< 4.17.0 | 4.17.0npm install mongodb@4.17.0 |
| 📦npm | mongodb | ≥ 5.0.0&&< 5.8.0 | 5.8.0npm install mongodb@5.8.0 |
| 🐘Packagist | mongodb/mongodb | ≥ 1.0.0&&< 1.9.2 | 1.9.2composer require mongodb/mongodb:^1.9.2 |
| 📦SwiftURL | github.com/mongodb/mongo-swift-driver | ≥ 1.0.0&&< 1.1.1 | 1.1.1 |
Affected Products
c drivermongodbc\+\+mongodbnode.jsmongodbphp drivermongodbswift drivermongodbDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mongodb to 3.6.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vxvm-qww3-2fh7 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-vxvm-qww3-2fh7 in your dependencies?
Find it across npm, Packagist, SwiftURL, including transitive dependencies.