CVE-2026-9742 json
Authenticate command with specific mechanism parameter can trigger server crash
published 2026-06-09 5 mo ago modified 2026-09-08 2 mo ago also BIT-mongodb-2026-9742 , EUVD-2026-35860
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
When OIDC authentication is enabled in configuration, clients may set specific values in the "mechanism" parameter of the "authenticate" command that lead to server crash. The authenticate command is accessible to unauthenticated clients, leading to pre-auth denial-of-service in affected product configurations.
Patch / fix
- bitnami mongodb 8.2.10, 8.3.3
- MongoDB MongoDB Server 8.2.10, 8.3.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mongodb | >=8.2.0, <8.2.10 >=8.3.0, <8.3.3 |
8.2.10 8.3.3 |
Affected products
- MongoDB MongoDB Server
Classification
- Weakness
-
- CWE-1287 Improper Validation of Specified Type of Input
- Technology feeds
References
-
jira.mongodb.org
/browse/SERVER-124183
patch, vendor-advisory, issue-tracking, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-9742
web
Sources
- CVE List CVE-2026-9742
- NVD CVE-2026-9742
- OSV BIT-mongodb-2026-9742
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.