A flaw in libmongoc's SCRAM authentication implementation caused the client to continue the authentication handshake and transmit the client proof even when a nonce mismatch was detected in the server's first message. An unauthorized party with a man-in-the-middle position could exploit this by injecting a crafted server-first-message containing a controlled salt and low iteration count, then capturing the resulting client proof to perform offline password cracking. This vulnerability is mitigated by TLS, which is standard in production deployments.
CVE-2026-93394
Score 3.7 from GitHub Security Advisory published 2026-09-17. a secondary CVSS source baseline 3.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(high)
- EG Risk
- 17(Track)EG Risk 17/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
September 17, 2026
Last Modified
September 18, 2026
References (1)
- cna@mongodbhttps://jira.mongodb.org/browse/CDRIVER-6315
Vendor Advisories for CVE-2026-93394(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:08 UTCGHSA enrichment
- 2026-09-18 15:26 UTCEG score recompute
- 2026-09-18 15:26 UTCGHSA enrichment
- 2026-09-18 14:35 UTCEG score recompute
- 2026-09-18 14:35 UTCGHSA enrichment
- 2026-09-17 21:20 UTCEG score recompute
- 2026-09-17 20:34 UTCEG score recompute
- 2026-09-17 20:34 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-93394?
When was CVE-2026-93394 disclosed?
Is CVE-2026-93394 actively exploited?
What is the CVSS score of CVE-2026-93394?
How do I remediate CVE-2026-93394?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-93394
Is Your Infrastructure Affected by CVE-2026-93394?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.