Skip to main content

MongoDB Server EUVDEUVD-2026-56861

| CVE-2026-18703 LOW
Incorrect Authorization (CWE-863)
2026-08-11 mongodb GHSA-h22h-g2cf-r8hr
2.3
CVSS 4.0 · Vendor: mongodb

Severity by source

Vendor (mongodb) PRIMARY
2.3 LOW
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/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
vuln.today AI
4.2 MEDIUM

Network-reachable but requires a trusted certificate plus matching account (PR:L, AC:H); scope unchanged within MongoDB; no availability impact described.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mongodb).

CVSS VectorVendor: mongodb

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

3
Analysis Generated
Aug 11, 2026 - 23:01 vuln.today
Patch available
Aug 11, 2026 - 19:04 EUVD
CVE Published
Aug 11, 2026 - 18:33 cve.org
LOW 2.3

DescriptionCVE.org

An issue in MongoDB Server could allow a party with a valid client certificate and a corresponding user account to authenticate using a certificate-based authentication method, even when an administrator has configured the server to restrict authentication to other mechanisms. This could allow authentication through a method the administrator intended to disable.

AnalysisAI

MongoDB Server 8.3.x through 8.3.7 permits certificate-based authentication to succeed for a client holding a valid x.509 certificate and a corresponding user account, even when the administrator has explicitly configured the server to restrict allowable authentication mechanisms to other methods such as SCRAM. The vulnerability undermines deliberate access-control policy decisions rather than enabling unauthenticated access, meaning the attacker must already possess legitimate credential material. With a CVSS 4.0 score of 2.3, CISA SSVC exploitation status of 'none', and no public exploit identified at time of analysis, this is a low-urgency compliance and policy-integrity issue rather than an imminent exploitation threat.

Technical ContextAI

MongoDB Server supports multiple authentication mechanisms, including SCRAM-SHA-1, SCRAM-SHA-256, and x.509 certificate-based authentication, configurable via the authenticationMechanisms server parameter in mongod.conf or at runtime via setParameter. CWE-863 (Incorrect Authorization) identifies the root cause: the server's enforcement of the configured mechanism allowlist is insufficiently rigorous, allowing the x.509 authentication path to succeed for a client even when that mechanism has been removed from the administrator-defined allowable set. The affected CPE is cpe:2.3:a:mongodb:mongodb_server:*:*:*:*:*:*:*:*, with EUVD-2026-56861 narrowing the confirmed vulnerable range to the 8.3.x release line (8.3.0 through 8.3.7). The flaw is tracked upstream in MongoDB JIRA ticket SERVER-127863.

RemediationAI

Upgrade MongoDB Server to version 8.3.8 or later, which contains the vendor-released patch per JIRA ticket SERVER-127863 (https://jira.mongodb.org/browse/SERVER-127863); the fix boundary of 8.3.8 is confirmed by the EUVD-2026-56861 affected-version range. Where immediate upgrade is not feasible, administrators should audit MongoDB user accounts to identify all accounts that have an associated x.509 subject DN and temporarily revoke or expire the corresponding certificates at the CA or via mongod's certificate trust store - note that this will break legitimate certificate-based logins for those accounts until re-issuance. Additionally, review MongoDB audit logs (if auditLog is configured) for x.509 authentication events to detect any unauthorized use of this path. Verify the authenticationMechanisms configuration post-patch to confirm the intended policy is correctly enforced.

CVE-2013-1892 MEDIUM POC
6.0 Oct 01

MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo

CVE-2013-3969 MEDIUM POC
6.5 Oct 01

The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a

CVE-2018-13863 HIGH POC
7.5 Jul 10

The MongoDB bson JavaScript module (also known as js-bson) versions 0.5.0 to 1.0.x before 1.0.5 is vulnerable to a Regul

CVE-2026-25887 HIGH POC
7.2 Mar 06

Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut

CVE-2019-2386 HIGH POC
7.1 Aug 06

After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's

CVE-2012-6619 MEDIUM POC
6.4 Mar 06

The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to

CVE-2026-3431 CRITICAL
9.8 Mar 02

SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary

CVE-2024-8654 CRITICAL
9.8 Sep 10

MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle

CVE-2024-6376 CRITICAL
9.8 Jul 01

MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e

CVE-2024-1351 CRITICAL
9.8 Mar 07

Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma

CVE-2020-7610 CRITICAL
9.8 Mar 30

All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8

CVE-2026-19001 CRITICAL
9.5 Aug 12

Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or

Share

EUVD-2026-56861 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy