EUVD-2026-57551
GHSA-gxxm-9rmv-h4mp
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/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
User must be induced to connect to the malicious deployment (UI:R); OS protocol handler invocation represents a scope change beyond the driver (S:C); impacts are user-context-limited credential theft and conditional code execution.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
Lifecycle Timeline
2DescriptionCVE.org
MongoDB Schema Manager and MongoDB Atlas SQL ODBC Driver do not validate the scheme of the authorization and token endpoints returned by an OIDC issuer's discovery document. A user induced to connect to an uncontrolled MongoDB deployment using MONGODB-OIDC authentication may have an uncontrolled URI dispatched to their operating system's default protocol handler, potentially exposing credentials or, under certain conditions, resulting in code execution in the user's context.
AnalysisAI
MongoDB Atlas SQL ODBC Driver and Schema Builder CLI fail to validate URI schemes in authorization and token endpoints returned by an OIDC issuer's discovery document, allowing an attacker-controlled MongoDB deployment to dispatch arbitrary URIs to a victim's operating system protocol handler. Users employing MONGODB-OIDC authentication who are induced to connect to a rogue or compromised MongoDB deployment may have OIDC credentials exposed or, under conditions where a dangerous OS protocol handler is registered, experience code execution within their user session context. No public exploit has been identified at time of analysis, and exploitation carries meaningful social engineering prerequisites that constrain real-world reach despite the network-accessible attack vector.
Technical ContextAI
Both affected components - MongoDB Atlas SQL ODBC Driver (CPE: cpe:2.3:a:mongodb:atlas_sql_odbc_driver) and MongoDB Schema Builder CLI (CPE: cpe:2.3:a:mongodb:schema_builder_cli) - implement MONGODB-OIDC authentication, which uses OpenID Connect discovery: clients fetch a well-known JSON document from the configured issuer, which declares authorization_endpoint and token_endpoint URI values. The root cause is CWE-20 (Improper Input Validation): neither component validates the URI scheme of these endpoint values before passing them to the operating system for dispatch. A malicious OIDC discovery document can return non-HTTPS schemes such as file://, ms-msdt://, or custom registered handlers, triggering OS-level protocol dispatch - a technique known as URI scheme abuse or protocol handler hijacking. The wildcard version entries in both CPE strings indicate all published versions of both products are affected, with no floor or ceiling version specified in available data.
RemediationAI
Upgrade both MongoDB Atlas SQL ODBC Driver and MongoDB Schema Builder CLI to the patched releases documented in the MongoDB SQL Interface changelog at https://www.mongodb.com/docs/sql-interface/changelog - exact fixed version numbers are not independently confirmed from available input data and must be verified directly from that source. As an immediate compensating control, restrict client workstations to connecting only to trusted, organization-managed MongoDB deployments by enforcing network-layer allowlists or firewall rules that prevent connections to arbitrary MongoDB endpoints; this eliminates the attacker-controlled-deployment prerequisite. Disabling MONGODB-OIDC as the authentication mechanism in client configurations and falling back to x.509 certificate or SCRAM authentication removes the attack surface entirely, though this will break existing SSO and identity-provider integrations and requires coordination with authentication infrastructure teams. Where MONGODB-OIDC must remain enabled, organizations should audit which protocol handlers are registered on client operating systems and remove or restrict dangerous handlers (file://, ms-msdt://, custom schemes) to limit the code-execution outcome while the credential-exposure risk remains.
MongoDB before 2.0.9 and 2.2.x before 2.2.4 does not properly validate requests to the nativeHelper function in SpiderMo
The find prototype in scripting/engine_v8.h in MongoDB 2.4.0 through 2.4.4 allows remote authenticated users to cause a
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
Remote code execution in Chartbrew versions prior to 4.8.1 allows authenticated attackers with high privileges to execut
After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user's
The default configuration for MongoDB before 2.3.2 does not validate objects, which allows remote authenticated users to
SimStudio below 0.5.74 has a missing authorization on MongoDB tool endpoints that allows attackers to execute arbitrary
MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are calle
MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of e
Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which ma
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. Rated critical severity (CVSS 9.8
Memory corruption in the MongoDB BI Connector ODBC Driver (fixed in v1.4.9) occurs when an oversized catalog, schema, or
Same weakness CWE-20 – Improper Input Validation
View allShare
External POC / Exploit Code
Leaving vuln.today