dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2025-11575

HIGH · 7.8 CVSS v3.1 Published 2025-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Incorrect Default Permissions vulnerability in MongoDB Atlas SQL ODBC driver on Windows allows Privilege Escalation.This issue affects MongoDB Atlas SQL ODBC driver: from 1.0.0 through 2.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The MongoDB Atlas SQL ODBC driver (versions 1.0.0-2.0.0) on Windows installs with overly permissive default file or folder permissions, allowing low-privileged users to modify executable files, DLLs, or configuration files that are subsequently loaded or executed by higher-privileged processes, enabling local privilege escalation.

MitigationApply the vendor patch when available; until then, manually review and restrict permissions on the ODBC driver installation directory to follow least-privilege principles (remove write access for non-admin users).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MongoDB Atlas SQL ODBC driver is installed
    Search for the driver in standard Windows installation locations: typically in Program Files or Program Files (x86) under a folder containing 'MongoDB Atlas SQL ODBC Driver' or similar naming. Also check Windows Programs and Features (Add or Remove Programs) for an entry named 'MongoDB Atlas SQL ODBC Driver'.
    Affected if The driver is present on the system.
  2. Identify the installed version
    Right-click the driver installation folder, select Properties, then look for version information. Alternatively, right-click any .exe or .dll file within the driver folder, select Properties, and check the Details tab for the product version.
    Affected if The installed version falls within the range 1.0.0 through 2.0.0 (inclusive).
  3. Examine folder permissions on the driver installation directory
    Right-click the driver installation folder, select Properties, go to the Security tab, and click Advanced. Review the permissions entries, specifically checking if Users or other non-administrator groups have Write or Full Control permissions on this folder.
    Affected if Non-admin users (such as the Users group) have Write, Modify, or Full Control permissions to the driver installation directory or its subdirectories.
  4. Verify permissions on executable and DLL files within the driver folder
    Within the driver installation folder, right-click on .exe and .dll files (particularly the main driver executable and any SQL*.dll files), select Properties, then Security. Check if standard users have Write or Modify permissions on these files.
    Affected if Standard (non-privileged) users can modify, replace, or overwrite executable files or DLLs used by the driver.
  5. Check permissions on configuration files in the driver directory
    Look for configuration files in the driver installation folder (commonly .ini, .cfg, or .json files). Right-click each, select Properties, then Security, and verify if non-admin users have Write permissions.
    Affected if Non-admin users can modify driver configuration files that get loaded by higher-privileged processes.

A system is affected if the MongoDB Atlas SQL ODBC driver versions 1.0.0-2.0.0 is installed and the installation directory or its contents grant Write permissions to non-administrative users, allowing potential privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available; until then, manually review and restrict permissions on the ODBC driver installation directory to follow least-privilege principles (remove write access for non-admin users).

Recommended fix Moderate confidence

MongoDB Atlas SQL ODBC driver version 2.0.1 or later

  1. Identify the currently installed MongoDB Atlas SQL ODBC driver version on the Windows system via ODBC Data Source Administrator or by checking the driver properties
  2. Navigate to the official MongoDB download center or software repository to obtain the latest version of the MongoDB Atlas SQL ODBC driver
  3. Download the latest Windows installer for the MongoDB Atlas SQL ODBC driver
  4. Backup any existing DSN configurations or connection strings that reference the current driver
  5. Uninstall the current MongoDB Atlas SQL ODBC driver through Windows Add or Remove Programs
  6. Run the downloaded installer for the latest driver version and complete the installation wizard
  7. Verify the new driver version is correctly installed by checking the driver details in ODBC Data Source Administrator
  8. Reconfigure any DSN connections that were using the previous driver to ensure they point to the newly installed driver version
Caveat Review release notes for any breaking changes between 2.0.0 and the target upgrade version, particularly regarding compatibility with existing SQL clients and connection string formats

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11575 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11575 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data