MongoDB BI Connector
CVE-2025-12100
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as local low-privileged user
-
DeliveryLocate world-writable custom install directory
-
ExploitPlant malicious binary/DLL
-
ExecutionTrigger execution in privileged context
-
ImpactGain administrator/SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the BI Connector ODBC driver (versions 1.0.0 through 1.4.6) was installed on Windows to a CUSTOM installation path, where the installer set overly permissive (insecure default) directory permissions; this is the exact condition the v1.4.7 fix addresses. Limiting factors: the attacker must already have authenticated local access as a low-privileged user (AV:L, PR:L), there is no remote vector, and the AT:P requirement plus the custom-path dependency mean default installations to standard protected directories are likely not affected - significantly narrowing real-world exposure despite the high CVSS impact scores. |
| Impact | This is a local privilege escalation flaw (CWE-276, Incorrect Default Permissions) that the vendor CVSS 4.0 vector scores 8.8 by rating all impact metrics High (VC:H/VI:H/VA:H) plus subsequent-system impact (SC:H/SI:H/SA:H). The critical nuance is in the exploitability metrics: AV:L means it is NOT remotely exploitable, PR:L means an attacker must already be an authenticated low-privileged local user, and AT:P indicates a specific attack requirement (per the fix, a non-default custom installation path). EPSS is very low (0.17%, 5th percentile) and there is no KEV listing and no public exploit identified, which is fully consistent with a local-only, condition-dependent escalation bug that is unattractive for mass exploitation. The headline 8.8 therefore overstates practical urgency: this is a genuine post-compromise privilege-escalation primitive, not an internet-facing or wormable issue. Signals are internally consistent (local vector + low EPSS + no KEV), so there is no conflict to flag - the main caveat is that the elevated impact scoring assumes escalation to full administrative/SYSTEM control of the Windows host. |
| Exploit ScenarioDerived | A low-privileged user already present on a Windows machine where the MongoDB BI Connector ODBC driver (<=1.4.6) was installed to a custom path with incorrectly permissive default ACLs replaces or plants a file/binary in that writable directory, which is then executed by a higher-privileged context, yielding escalation to administrator/SYSTEM. No public exploit code has been identified at time of analysis, and the attack requires prior local access plus the non-default installation condition. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Local privilege escalation in MongoDB BI Connector ODBC driver versions 1.0.0 through 1.4.6 occurs when the Windows installer is used to place the driver in a custom installation path, because the installer applies overly permissive directory permissions that a low-privileged local user can leverage to elevate privileges. Affected systems are Windows hosts running the BI Connector ODBC driver with a non-default install location; default installations into standard protected directories are likely unaffected. Exploitation requires authenticated local access as a low-privileged user plus the custom-path precondition, and no public exploit code has been identified at time of analysis (EPSS 0.17%, 5th percentile, no CISA KEV listing).
RemediationAI
Vendor-released patch: upgrade the MongoDB BI Connector ODBC driver to version 1.4.7 or later, which the vendor release notes explicitly state fixes CVE-2025-12100 'by correcting permissions for custom installation paths' (https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.7). If immediate upgrade is not possible, inspect and harden the ACLs on any custom installation directory used by the driver so that non-privileged local users cannot write to the driver directory or its DLLs and configuration files; this can be done with icacls or equivalent, but note the trade-off that restrictive ACLs may break legitimate non-admin update or repair operations and should be tested before broad rollout. Additionally, avoid custom installation paths on future deployments and prefer the installer's default protected location, and consider restricting interactive local logon or privilege boundaries on hosts where a low-privileged user could otherwise exploit a writable driver directory. No vendor workaround beyond the version 1.4.7 upgrade or manual permission correction is identified in the available data.
Affected ProductsAI
The MongoDB BI Connector ODBC driver for Windows is affected in versions 1.0.0 through 1.4.6 inclusive, as published in the upstream repository at https://github.com/mongodb/mongo-bi-connector-odbc-driver. The vulnerability only manifests when the driver was installed to a custom installation path, where the installer assigned incorrect default permissions to that directory; installations performed into the default, properly protected locations are not expected to be exploitable. The vendor's release page for the fixed version is at https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.7, and the NVD reference set documents the same advisory endpoint.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-276 (Incorrect Default Permissions): the MongoDB BI Connector ODBC driver's Windows installer creates the chosen custom installation directory with insecure default ACLs, leaving files and the directory writable by non-privileged users. Because the driver is a native library loaded into processes such as BI/reporting clients or ODBC-consuming services, an attacker with local authenticated access can place or modify DLLs or configuration within that writable path and have a higher-privileged process load them, achieving code execution in a more privileged context. The vendor's CVSS 4.0 vector (8.8) rates all vulnerable-system and subsequent-system impacts High (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H), while the independent assessment applies CVSS 3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, reflecting the meaningful attack-complexity and custom-install-path constraints that narrow exploitability despite the high impact metrics. The relevant CPE/product family is the MongoDB BI Connector ODBC driver under the mongodb namespace, with source-code evidence from the upstream GitHub repository confirming the scope of the fix.
Know when MongoDB gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Local-only (AV:L) escalation needing an existing low-priv account (PR:L) and a non-default custom-path condition (AC:H); successful escalation yields full host control, so C/I/A:H.
Primary rating from Vendor (mongodb).
CVSS VectorVendor: mongodb
DescriptionCVE.org
Incorrect Default Permissions vulnerability in MongoDB BI Connector ODBC driver allows Privilege Escalation.This issue affects BI Connector ODBC driver: from 1.0.0 through 1.4.6.
Executive ViewAI
MongoDB BI Connector ODBC driver versions 1.0.0 through 1.4.6 on Windows, when installed to a non-default location, may allow a local user to gain elevated privileges on the host. This could let a malicious insider or an attacker with existing low-privileged access expand their control, potentially leading to unauthorized data access or further compromise of affected systems. Because only custom-path installations on Windows are affected and no public exploit identified at time of analysis, the immediate organizational risk is contained, but unpatched exposure on business-critical endpoints warrants management attention.
Restrict NTFS permissions on the custom installation directory to Administrators and SYSTEM, reinstall the driver to the default protected path where possible, and limit local low-privileged user access on affected Windows hosts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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
NVD
CVE.org
EPSS
GitHub
Exploit-DB