MongoDB Shell (mongosh) bundled with Node.js trusts certificates issued by recoverable eMudhra intermediate CAs
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.14.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The MongoDB Shell (mongosh) is affected because its bundled Node.js runtime trusts intermediate certificate authorities from eMudhra that can be recovered, which could allow an attacker to impersonate secure websites or services and intercept encrypted connections. If mongosh was installed through npm, the risk comes from the Node.js runtime on the host, which must be updated separately.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
The MongoDB Shell (mongosh) relies on Node.js as a third-party runtime that carries its own TLS root certificate store. This certificate store has the recoverable eMudhra intermediate CA certificates. This issue impacts MongoDB Shell (mongosh) versions prior to 2.14.0 and can be resolved by updating to mongosh 2.14.0 which bundles Node.js 24.22.1 or later. If mongosh is installed through npm, it uses the Node.js runtime installed on the host; update that runtime separately.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- MongoDB, Inc. mongosh
fixed in 2.14.0