Skip to main content

MongoDB Connector for BI CVE-2025-11535

HIGH
Incorrect Default Permissions (CWE-276)
2025-10-08 cna@mongodb.com
8.8
CVSS 4.0 · Vendor: mongodb
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Delivery
    Write payload to weak-ACL custom install directory
  3. Exploit
    Replace Connector binary or DLL
  4. Execution
    Code executed by privileged process
  5. Impact
    Escalate to higher/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 MongoDB Connector for BI (versions 2.0.0 through 2.14.24) was installed via the Windows MSI installer to a CUSTOM (non-default) install directory, where the installer fails to set restrictive ACLs, leaving the directory writable by non-privileged users. The attacker must already be an authenticated low-privileged local user on the Windows host (PR:L, AV:L). Limiting factors: default install locations are reportedly not affected, so only custom-path installations are vulnerable; the flaw is Windows/MSI-specific and does not apply to other platforms; remote exploitation is not possible; and a privileged process or user must subsequently execute code from the weakly-permissioned directory for escalation to occur.

Impact

This is a genuine but conditional local privilege-escalation issue (CWE-276, Incorrect Default Permissions) rather than a broadly exploitable remote flaw. The only CVSS vector provided is 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, base 8.8): local attack vector, low complexity, but a Present attack requirement (AT:P) and Low privileges (PR:L) already required, meaning the attacker must be an authenticated local user and specific conditions (a custom install directory with unset ACLs) must hold. The high score is driven by full confidentiality/integrity/availability impact once escalation succeeds, not by ease of reach. Corroborating signals point to low real-world urgency: EPSS is only 0.12% (2nd percentile), there is no CISA KEV listing, and no public exploit code was identified. No SSVC decision data was supplied. The vendor's CVSS 4.0 marks subsequent-system impact as High (SC/SI/SA:H), which somewhat inflates the score for what is essentially single-host compromise; I independently assess subsequent-system impact as None. Net: a real but low-priority issue for most defenders - patch on normal cadence, prioritize only hosts where the Connector was installed to a non-default directory.

Exploit ScenarioDerived

No public exploit code was identified. On a Windows host where MongoDB Connector for BI (2.0.0-2.14.24) was installed via MSI to a custom (non-default) directory, a low-privileged local user who already has access to the machine writes a malicious binary or DLL into the install directory, which inherits overly permissive ACLs. When a higher-privileged user or service later executes the Connector, the attacker's code runs with those elevated privileges. Because the attack vector is local (AV:L) with a present attack requirement, exploitation is confined to existing local users on affected installations.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Local privilege escalation in MongoDB Connector for BI 2.0.0 through 2.14.24 on Windows allows an authenticated low-privileged user to obtain elevated privileges when the product was installed via the MSI package into a custom (non-default) directory. The installer fails to set restrictive ACLs on that custom directory, so a non-privileged local user who can write to it can plant or modify files that a privileged process subsequently executes (CWE-276, Incorrect Default Permissions); exploitation is local, requires an existing foothold on the host, and only matters for custom-path installations, as default install locations are reportedly unaffected. No public exploit code has been identified at time of analysis and exploitation has not been confirmed in the wild; EPSS is very low at roughly 0.12 percent (2nd percentile), and MongoDB addressed the issue in the 2.14.25 release.

RemediationAI

Vendor-released patch: upgrade to MongoDB Connector for BI 2.14.25 or later, per the release notes at https://www.mongodb.com/docs/bi-connector/current/release-notes/#bi-2.14.25; organizations that cannot upgrade immediately should inventory installations and prioritize Windows hosts where the MSI was pointed at a custom directory. For those custom-path installations, either uninstall and reinstall the connector into the default Program Files location (which carries the proper inherited ACLs) or manually harden the directory with an ACL tool such as icacls, removing write, create-file, and delete rights for Users, Authenticated Users, and any other non-administrative principals while granting full control only to Administrators and SYSTEM; the trade-off is that overly aggressive ACLs can break the connector's own service account or log-writing behavior, so the effective permissions should be tested before relying on them. Additional compensating controls include restricting interactive logon on hosts running privileged automation that consumes the connector, and monitoring for unexpected file creation or modification in the connector's install directory, which would indicate binary-planting activity. Because exploitation requires a pre-existing low-privileged local account, hardening local account provisioning and reducing the number of users with interactive access to affected servers lowers exposure while the patch is rolled out.

Affected ProductsAI

MongoDB Connector for BI versions 2.0.0 through 2.14.24 are affected, and only when the product is installed on Windows using the MSI installer with a custom, non-default install directory; default install paths are reportedly not vulnerable. No CPE strings or vendor CPE mappings were supplied with this record, so affectedness should be confirmed against the version range and the MongoDB release notes rather than through CPE matching. The issue is fixed in MongoDB Connector for BI 2.14.25, as documented in the vendor release notes at https://www.mongodb.com/docs/bi-connector/current/release-notes/#bi-2.14.25. Other platforms and non-MSI deployment methods for the same version range are not described as vulnerable.

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) in the Windows MSI-based installer for MongoDB Connector for BI. When a user directs the MSI to a custom installation directory, the installer creates that directory without applying the restrictive DACL that a default location such as Program Files inherits, leaving the folder writable by non-administrative local users. Because the directory holds binaries and libraries belonging to the Connector for BI (and its bundled components), a local attacker with write access can plant a malicious DLL or replace an executable and wait for a privileged context - an administrative user, service, or scheduled task - to load or run it, converting weak directory permissions into code execution at higher integrity. The published vector is CVSS v4.0 8.8 (AV:L/AC:L/AT:P/PR:L/UI:N, high confidentiality/integrity/availability on both vulnerable and subsequent systems), while the independent assessment scores it CVSS v3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H); both agree the attack is local and requires an authenticated low-privileged user, and the independent analysis explicitly treats it as a conditional local escalation rather than a remotely exploitable flaw. The vulnerability surface is Windows/MSI-specific and does not extend to other platforms or to installations made with non-MSI methods.

Know when Windows 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

Vendor (mongodb) PRIMARY 8.8 HIGH
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
vuln.today AI 7.8 HIGH

Local privilege escalation by an existing low-privileged user (AV:L, PR:L); weak directory ACLs make the write straightforward (AC:L); successful binary replacement yields full host compromise (C/I/A:H).

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

Primary rating from Vendor (mongodb).

CVSS VectorVendor: mongodb

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

DescriptionCVE.org

MongoDB Connector for BI installation via MSI on Windows leaves ACLs unset on custom install directories allows Privilege Escalation.This issue affects MongoDB Connector for BI: from 2.0.0 through 2.14.24.

Executive ViewAI

Why It Matters

MongoDB Connector for BI versions 2.0.0 through 2.14.24 installed via MSI into custom Windows directories contain a local privilege escalation flaw that could allow a local user with existing access to gain elevated privileges on the host. While exploitation requires an existing local foothold and only affects custom-path installations, successful abuse could lead to unauthorized administrative control, data access, or lateral movement. With no public exploit identified at time of analysis and a very low EPSS, leadership should prioritize identifying and remediating affected installations, especially in environments with non-default deployments.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Low
specialized MongoDB BI tool, limited Windows-only deployment footprint
Data Quality
3 sources
Confidence: Low

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
Medium

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

CVE-2026-96951 HIGH POC
8.8 Oct 13

Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then

CVE-2025-24054 MEDIUM POC
6.5 Mar 11

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network

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