<?xml version="1.0" encoding="UTF-8" ?>
      <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
      <channel>
      <title>MongoDB | Product Alerts</title>
      <description>MongoDB news and information.</description>
      <link>https://www.mongodb.com/resources/products/alerts</link>
  
    <item>
      <title></title>
      <description><![CDATA[<p>Possible buffer overflow may result cause in-memory corruption on MongoDB 4.2.7 with incremental backup enabled.</p>
]]></description>
      <pubDate>Tue, 16 Jun 2020 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-6366</link>
      <guid>https://jira.mongodb.org/browse/WT-6366</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A race condition in WiredTiger may prevent a write operation from becoming immediately visible to subsequent read operations, which may result in various problems, primarily impacting replication.</p>
]]></description>
      <pubDate>Wed, 09 Dec 2015 20:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-21275</link>
      <guid>https://jira.mongodb.org/browse/SERVER-21275</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>In a replica set, if a secondary node is shut down cleanly while replicating writes, the node may mark certain replicated operations as successfully applied even though they have not.</p>
]]></description>
      <pubDate>Wed, 16 Dec 2015 20:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/2</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>During chunk migrations, insert and update operations affecting data within a migrating chunk are not reflected to the recipient shard, resulting in data loss.</p>
]]></description>
      <pubDate>Wed, 30 Mar 2016 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-23425</link>
      <guid>https://jira.mongodb.org/browse/SERVER-23425</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>While a background index build is in progress, document updates modifying fields contained in the index specification may, under specific circumstances, cause mismatched index entries to appear. This has an impact on queries that use affected indexes.</p>
]]></description>
      <pubDate>Tue, 03 May 2016 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-22970</link>
      <guid>https://jira.mongodb.org/browse/SERVER-22970</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>We have identified a bug in MongoDB Compass where modification or deletion of a document through Compass may occur on a different document than expected under certain specific conditions.</p>
]]></description>
      <pubDate>Thu, 22 Feb 2018 20:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-compass-feb-2018</link>
      <guid>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-compass-feb-2018</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A memory management bug can cause failed operations, process crashes, and in-memory corruption of data that may be persisted to disk.</p>
]]></description>
      <pubDate>Mon, 23 Sep 2019 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-42744</link>
      <guid>https://jira.mongodb.org/browse/SERVER-42744</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When MongoDB recovers from an unclean shutdown, it is possible for the recovery process to corrupt documents that have received size-changing updates.</p>
]]></description>
      <pubDate>Tue, 07 Jan 2020 20:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-44584</link>
      <guid>https://jira.mongodb.org/browse/SERVER-44584</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A memory management bug can cause lost documents and index inconsistencies on replica set secondaries that restart during index builds.</p>
]]></description>
      <pubDate>Thu, 09 Jan 2020 20:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-43882</link>
      <guid>https://jira.mongodb.org/browse/SERVER-43882</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Sharded clusters where the balancer is enabled (or there are manual chunk migrations), containing WiredTiger nodes that may become primary, may lose writes to a chunk being migrated if that chunk is under a heavy write load.</p>
]]></description>
      <pubDate>Mon, 15 Jun 2015 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-18822</link>
      <guid>https://jira.mongodb.org/browse/SERVER-18822</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Possible Corruption of Backup Snapshots on certain MongoDB 4.2+ Products</p>
]]></description>
      <pubDate>Mon, 12 Oct 2020 19:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-snapshot-corruption-oct-2020</link>
      <guid>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-snapshot-corruption-oct-2020</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine bug in MongoDB 4.4.5 causes crashes on startup and may cause temporary query correctness issues. Upgrade to version 4.4.6.</p>
]]></description>
      <pubDate>Wed, 19 May 2021 19:22:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-7426</link>
      <guid>https://jira.mongodb.org/browse/WT-7426</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine bug in MongoDB 4.4.7, 5.0.0, and 5.0.1 allows some inserts to violate unique index constraints. Upgrade to version 4.4.8 or 5.0.2.</p>
]]></description>
      <pubDate>Fri, 06 Aug 2021 17:41:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-58936</link>
      <guid>https://jira.mongodb.org/browse/SERVER-58936</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine bug in MongoDB 4.4.8 can cause inconsistent data after an unclean shutdown and restart. Upgrade to version 4.4.9</p>
]]></description>
      <pubDate>Wed, 22 Sep 2021 16:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-7984</link>
      <guid>https://jira.mongodb.org/browse/WT-7984</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine bug in MongoDB 4.4.2 - 4.4.8, and 5.0.0 - 5.0.2 can cause inconsistent data after an unclean shutdown and restart. Upgrade to version 4.4.9 or 5.0.3.</p>
]]></description>
      <pubDate>Wed, 22 Sep 2021 16:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-7995</link>
      <guid>https://jira.mongodb.org/browse/WT-7995</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>&quot;A storage engine bug in MongoDB 4.4.3 and 4.4.4 can introduce corruption when upgrading to 4.4.8-4.4.10 or 5.0.2-5.0.5. It is safe to upgrade from versions 4.4.3 and 4.4.4 directly to 4.4.11+ or 5.0.6+&quot;1</p>
]]></description>
      <pubDate>Fri, 12 Nov 2021 00:02:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-8395</link>
      <guid>https://jira.mongodb.org/browse/WT-8395</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A sharding metadata bug in MongoDB versions 5.0.0-5.0.10 and 6.0.0 can introduce corruption during a movePrimary command.</p>
]]></description>
      <pubDate>Wed, 10 Aug 2022 21:31:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-68511</link>
      <guid>https://jira.mongodb.org/browse/SERVER-68511</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A behavior change for improperly configured time-to-live (TTL) indexes can suddenly expire documents when upgrading to MongoDB 5.0 or 6.0 from version 4.4 or earlier.</p>
]]></description>
      <pubDate>Thu, 11 Aug 2022 20:20:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-68477</link>
      <guid>https://jira.mongodb.org/browse/SERVER-68477</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When MongoDB is configured for FIPS mode on Linux operating systems which use OpenSSL 3 for cryptographic operations, MongoDB may use cryptographic algorithms from non-FIPS providers. This may allow clients to connect to a FIPS-mode MongoDB with TLS using non-FIPS-compliant cryptographic algorithms.</p>
]]></description>
      <pubDate>Thu, 11 Sep 2025 11:01:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-109268</link>
      <guid>https://jira.mongodb.org/browse/SERVER-109268</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>MongoDB is actively investigating a security incident involving unauthorized access to certain MongoDB corporate systems, which includes exposure of customer account metadata and contact information. We detected suspicious activity on Wednesday (Dec. 13th, 2023) evening US Eastern Standard Time, immediately activated our incident response process, and believe that this unauthorized access has been going on for some period of time before discovery. At this time, we are not aware of any exposure to the data that customers store in MongoDB Atlas. Nevertheless, we recommend that customers be vigilant for social engineering and phishing attacks, activate phishing-resistant multi-factor authentication (MFA), and regularly rotate their MongoDB Atlas passwords. MongoDB will update this alert page with additional information as we continue to investigate the matter.</p>
]]></description>
      <pubDate>Sat, 16 Dec 2023 20:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/19#2</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>We are experiencing a spike in login attempts resulting in issues for customers attempting to log in to Atlas and our Support Portal. This is unrelated to the security incident. Please try again in a few minutes if you are still having trouble logging in. [The issue involving user login attempts has been resolved as of 10:22 PM EST]</p>
]]></description>
      <pubDate>Tue, 26 Dec 2023 22:25:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/20#3</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>At this time, we have found no evidence of unauthorized access to MongoDB Atlas clusters. To be clear, we have not identified any security vulnerability in any MongoDB product as a result of this incident. It is important to note that MongoDB Atlas cluster access is authenticated via a separate system from MongoDB corporate systems, and we have found no evidence that the Atlas cluster authentication system has been compromised.We are aware of unauthorized access to some corporate systems that contain customer names, phone numbers, and email addresses among other customer account metadata, including system logs for one customer. We have notified the affected customer. At this time, we have found no evidence that any other customers system logs were accessed.We are continuing with our investigation, and are working with relevant authorities and forensic firms. MongoDB will update this alert page with additional information as we continue to investigate the matter.</p>
]]></description>
      <pubDate>Thu, 28 Dec 2023 02:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/21#4</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>We continue to find no evidence of unauthorized access to MongoDB Atlas clusters or the Atlas cluster authentication system. Our investigation and work with the relevant authorities is ongoing. MongoDB will update this alert page with pertinent information as we further investigate the matter. At this time, as a result of our investigation in collaboration with outside experts, we have high confidence that we were victims of a phishing attack. Through our investigation, we have identified certain information that may be helpful to protect yourself against a potential attack by this unauthorized partyIndicators of Compromise (IOCs)The unauthorized party used the Mullvad VPN.  Mullvad has many external IP addresses, and there are many VPNs that can be used to hide an IP address.  In this case, we saw malicious activity coming from the following IP addresses:107.150.22.47138.199.6.199146.70.187.157179.43.189.85185.156.46.165198.44.136.69198.44.136.71198.44.140.133198.44.140.199199.116.118.207206.217.205.8866.63.167.15266.63.167.15487.249.134.1096.44.191.132We recommend using the above information to search your networks for suspicious activity. We are committed to being as transparent in this process as we can and providing information so you can assess risk in your network.In regards to our previous guidance, instructions can be found here <a href="https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/">https://www.mongodb.com/docs/atlas/security-multi-factor-authentication/</a> on how to enable phishing-resistant MFA on MongoDBs native cloud authentication service. MongoDB Cloud also supports federating your identity from your IDP, please see here: <a href="https://www.mongodb.com/docs/atlas/security/federated-authentication/We">https://www.mongodb.com/docs/atlas/security/federated-authentication/We</a> have fielded questions from some customers about the authenticity of the e-mail titled: MongoDB Security Notice that our Chief Information Security Officer, Lena Smart, sent over the weekend from <a href="mailto:&#x6d;&#111;&#x6e;&#x67;&#111;&#100;&#98;&#116;&#101;&#x61;&#109;&#x40;&#109;&#x61;&#105;&#x6c;&#49;&#46;&#x6d;&#111;&#110;&#x67;&#111;&#100;&#98;&#46;&#99;&#x6f;&#x6d;">&#x6d;&#111;&#x6e;&#x67;&#111;&#100;&#98;&#116;&#101;&#x61;&#109;&#x40;&#109;&#x61;&#105;&#x6c;&#49;&#46;&#x6d;&#111;&#110;&#x67;&#111;&#100;&#98;&#46;&#99;&#x6f;&#x6d;</a>.  We can confirm that this email is legitimate.</p>
]]></description>
      <pubDate>Fri, 29 Dec 2023 05:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/22#5</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>Our investigation of the security incident first reported here on December 16, 2023, US Eastern time (EST) is now <strong>complete and closed</strong>.The investigation led by our security and engineering teams uncovered no evidence of unauthorized access to MongoDB Atlas clusters. This finding has been verified by our third-party forensic experts.We are committed to being timely and transparent with details about this Security Incident. We plan to release a post event summary as soon as practicable.</p>
]]></description>
      <pubDate>Wed, 03 Jan 2024 22:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/23#6</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>Our investigation of the security incident first reported here on December 16, 2023, US Eastern time (EST) is now <strong>complete and closed</strong>.The investigation led by our security and engineering teams uncovered no evidence of unauthorized access to MongoDB Atlas clusters. This finding has been verified by our third-party forensic experts.We are committed to being timely and transparent with details about this Security Incident. We plan to release a post event summary as soon as practicable.</p>
]]></description>
      <pubDate>Thu, 04 Jan 2024 01:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/24#7</guid>
    </item>
    <item>
      <title> (MongoDB Security Notice)</title>
      <description><![CDATA[<p>MongoDB has published MongoDB has published a Post Event Summary at the Reference link, below, for the first security incident reported here on December 16, 2023, US Eastern time (EST). As a reminder, our investigation is complete and closed, with our findings verified by our third-party forensic experts. </p>
]]></description>
      <pubDate>Wed, 24 Jan 2024 02:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/company/blog/news/mongodb-security-incident-post-event-summary-january-23-2024</link>
      <guid>https://www.mongodb.com/company/blog/news/mongodb-security-incident-post-event-summary-january-23-2024</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Caching of dbhash results may result in stale values, potentially causing disagreement among sharded cluster config servers.</p>
]]></description>
      <pubDate>Tue, 29 Oct 2013 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-11421</link>
      <guid>https://jira.mongodb.org/browse/SERVER-11421</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A MongoDB agent issue in Atlas, Ops Manager, and Cloud Manager can cause automated &quot;rolling index builds&quot; to introduce index inconsistencies. MongoDB clusters on other platforms are not affected.</p>
]]></description>
      <pubDate>Mon, 19 Sep 2022 12:56:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-rolling-index-build-issue-sept-2022</link>
      <guid>https://www.mongodb.com/resources/products/alerts/critical-alert-mongodb-rolling-index-build-issue-sept-2022</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Third-party distributions of the MongoDB Shell, such as those installed by the Homebrew or npm package managers, can be affected by a Node.js REPL bug that may cause unintended side effects to occur during autocomplete.</p>
]]></description>
      <pubDate>Tue, 30 Sep 2025 12:12:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOSH-2635</link>
      <guid>https://jira.mongodb.org/browse/MONGOSH-2635</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Major public Certificate Authorities are implementing policy requirements to stop issuing TLS certificates with client authentication (clientAuth) Extended Key Usage by April 2026. This industry-wide change only affects self-managed MongoDB deployments using mutual TLS (mTLS) or X.509 authentication with public CA certificates. Self-managed customers must migrate to private PKI infrastructure or reconfigure MongoDB before the April-May 2026 deadlines. Atlas customers are not affected.</p>
]]></description>
      <pubDate>Thu, 22 Jan 2026 15:46:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/public-certificate-authority-policy-changes-affecting-mtls</link>
      <guid>https://www.mongodb.com/resources/products/alerts/public-certificate-authority-policy-changes-affecting-mtls</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Secondary indexes (i.e. all indexes other than _id) may be corrupted on an initial sync if write operations are performed on the sync source during the initial sync.</p>
]]></description>
      <pubDate>Thu, 21 Mar 2013 19:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/30#8</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>During a chunk migration in a sharded cluster, if one of the documents in the chunk has a size in the range of 16,776,185 and 16,777,216 bytes (inclusive), then some documents may be lost during the migration process</p>
]]></description>
      <pubDate>Mon, 21 Oct 2013 19:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/31#9</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Under very rare circumstances mongos may incorrectly report a write as successful.</p>
]]></description>
      <pubDate>Wed, 01 Jan 2014 20:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/32#10</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>An update to a text-indexed field may fail to update the text index. As a result, a text search may not match the field contents, yielding incorrect search results.</p>
]]></description>
      <pubDate>Sun, 03 Aug 2014 19:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-14738</link>
      <guid>https://jira.mongodb.org/browse/SERVER-14738</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>MongoDB installations on certain 3.x Linux kernels running on VMWare and using virtual SCSI disks managed by LVM may see corruption in namespace (.ns) files.</p>
]]></description>
      <pubDate>Thu, 02 Oct 2014 07:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts</link>
      <guid>resources/products/alerts/34#11</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>If a cluster undergoes a point-in-time (PIT) restore at a wall-clock time significantly after the TransactionRecordMinimumLifetimeMinutes timeout has elapsed, cross-shard transactions may be silently partially committed while still being acknowledged as successfully completed to the client. This can also occur in other rare conditions; see reference link for details.</p>
]]></description>
      <pubDate>Thu, 20 Nov 2025 19:56:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-105751</link>
      <guid>https://jira.mongodb.org/browse/SERVER-105751</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Certain queries that involve an $elemMatch expression with string predicates may use an index with incompatible collation due to a plan cache bug. Impacted queries can return results which miss documents that should have been included. Write operations that rely on queries that incorrectly miss documents may not correctly update those documents. This includes updates, deletes, and $merge/$out aggregations with impacted query filters.</p>
]]></description>
      <pubDate>Tue, 17 Jun 2025 10:38:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-92806</link>
      <guid>https://jira.mongodb.org/browse/SERVER-92806</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Combined alert for MongoDB Relational Migrator with multiple data integrity issues affecting data migrations from relational databases into MongoDB. These affect Snapshot migrations that contain specific mappings for cyclic dependency loops, array-in-doc-in-array nested embeddings, or use of the idempotency user setting. These also affect Continuous (CDC) migrations.</p>
]]></description>
      <pubDate>Wed, 16 Jul 2025 12:51:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/relational-migrator-data-integrity-issues-2025</link>
      <guid>https://www.mongodb.com/resources/products/alerts/relational-migrator-data-integrity-issues-2025</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Performing deletes on time-series collection with a non-metaField filter followed by inserts on an adjacent time range, can result in data inserted after the delete to be prematurely TTL expired and/or missing from query results.</p>
]]></description>
      <pubDate>Thu, 07 Aug 2025 18:06:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-99527</link>
      <guid>https://jira.mongodb.org/browse/SERVER-99527</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Time series data can be corrupted if double-precision metrics are inserted in a pattern of multiple successive values with identical non-zero deltas, followed by a measurement where the metric is missing, into a time series collection for a specific meta value and adjacent time range.</p>
]]></description>
      <pubDate>Thu, 07 Aug 2025 18:14:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103328</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103328</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When restoring from a backup, mongorestore silently ignores namespaces containing a newline character, without logging any warning messages. This affects mongorestore versions 3.3.11-100.12.1. Please upgrade to version 100.12.2 or later. This issue also affects namespaces containing newlines on Atlas Flex-tier backup snapshots, and Free-tier clusters that have been in a paused state. In both these scenarios, Atlas uses mongorestore behind the scenes and the fix has already been applied.</p>
]]></description>
      <pubDate>Tue, 16 Sep 2025 11:10:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/TOOLS-3822</link>
      <guid>https://jira.mongodb.org/browse/TOOLS-3822</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Under certain situations, when running a join ($lookup, $graphLookup or $unionWith) in one database, followed by a $merge or $out written into another database, the join can read the wrong collection if the foreign collection of the join stage and the output collection of the $merge or $out stage have the same name. This will result in incorrect or missing results in the output collection.</p>
]]></description>
      <pubDate>Thu, 09 Oct 2025 10:42:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-96107</link>
      <guid>https://jira.mongodb.org/browse/SERVER-96107</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When running on a standalone replica set while using queryable encryption or on a sharded cluster, write concern errors may be incorrectly suppressed when write errors occur (such as duplicate key errors or schema validation errors) or when the create command completes successfully (in a sharded cluster). This can cause applications to incorrectly assume that prior writes were durable, resulting in silent data loss. This can only occur if a primary failover and rollback subsequently occur.</p>
]]></description>
      <pubDate>Thu, 20 Nov 2025 11:02:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-113256</link>
      <guid>https://jira.mongodb.org/browse/SERVER-113256</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>2dsphere indexes on metric data in time series collections are not correctly maintained when inserting data into the time series collection. Index keys may not be generated and inserted into the index, causing geospatial queries optimized by it to return incomplete results.</p>
]]></description>
      <pubDate>Thu, 20 Nov 2025 18:02:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-112520</link>
      <guid>https://jira.mongodb.org/browse/SERVER-112520</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A bug, under certain circumstances, may cause a simple equality (non-_id) predicate query on sharded collections to report no results when a valid result exists.</p>
]]></description>
      <pubDate>Mon, 28 Apr 2025 18:40:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-97860</link>
      <guid>https://jira.mongodb.org/browse/SERVER-97860</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Under certain conditions, including a failover, a cross-shard transaction with apiVersion explicitly set may be partially committed while still being acknowledged as successfully completed to the client. This can lead to a torn transaction in versions v8.0v8.0.12, or (in other affected versions) cause interruptions to subsequent operations on the documents affected by the transaction.</p>
]]></description>
      <pubDate>Thu, 20 Nov 2025 19:55:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106075</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106075</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Queries on a sharded collection which specify equalities on all fields of the sharding key and use any collation other than {locale: &quot;simple&quot;} may temporarily return duplicate records when chunks are being migrated between shards.</p>
]]></description>
      <pubDate>Thu, 29 Jan 2026 15:57:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-94315</link>
      <guid>https://jira.mongodb.org/browse/SERVER-94315</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>The SQL interface (Atlas and Enterprise Advanced) can return incorrect results when SQL queries contain a WHERE clause with an OR condition where one predicate evaluates to UNKNOWN and the other predicate evaluates to TRUE. This happens when the UNKNOWN predicates datasource contains a nullable field with null or missing values.</p>
]]></description>
      <pubDate>Thu, 12 Feb 2026 09:06:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SQL-3041</link>
      <guid>https://jira.mongodb.org/browse/SQL-3041</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Aggregation queries containing a $sort stage immediately followed by a $group stage with $top or $bottom accumulators can return incorrect results. This occurs when the query uses a compound index that satisfies the $sort pattern, but the accumulator&#39;s sort direction does not match the pipeline&#39;s $sort direction.</p>
]]></description>
      <pubDate>Tue, 17 Mar 2026 13:13:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-110803</link>
      <guid>https://jira.mongodb.org/browse/SERVER-110803</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Sharded collections with a compound wildcard index that includes the shard key as a prefix may be at risk of data loss during chunk migrations. Documents may be left behind on the donor shard if they are missing all fields defined in the compound wildcard index, or if the index uses descending order (e.g., {skey: 1, &quot;a.$**&quot;: -1}) and the document&#39;s shard key matches the min boundary of the migration.</p>
]]></description>
      <pubDate>Tue, 17 Mar 2026 18:05:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103774</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103774</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When connecting directly to shard nodes instead of through mongos (including during a replica set promotion to sharded cluster), cluster-wide default read/write concerns may not be honored, causing writes to use {w: 1} instead of configured concerns, potentially losing acknowledged writes if rollback occurs. Users should connect to sharded clusters exclusively through mongos. If a direct connection to a shard is required, users should upgrade to patched versions immediately or specify explicit read and write concerns (e.g., {w: &quot;majority&quot;}) in connection strings.</p>
]]></description>
      <pubDate>Thu, 14 May 2026 10:22:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-111031</link>
      <guid>https://jira.mongodb.org/browse/SERVER-111031</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>For users that have migrated with Relational Migrator: Sharded cluster migrations with embedded documents or embedded arrays may cause missing documents; Cyclic mappings with an excluded foreign key under an embedded array will be missing; A source table column used in multiple composite foreign key relationships can cause mismatched embeddings; Conflicting field name choices can cause omitted and mis-named fields.</p>
]]></description>
      <pubDate>Thu, 14 May 2026 07:32:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-126522</link>
      <guid>https://jira.mongodb.org/browse/SERVER-126522</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>The Node.js v22.7.0 runtime contains a regression related to its handling of UTF-8 encoding that can impact the data integrity of applications using the MongoDB Node.js driver. MongoDB does not use the affected Node.js version in any of its products, however, developers using MongoDBs Node.js driver could experience data integrity issues when data is written to their clusters via the Node.js v22.7.0 runtime.</p>
]]></description>
      <pubDate>Tue, 10 Sep 2024 13:09:00 GMT</pubDate>
      <link>https://mongodbcom.website.prod.corp.mongodb.com/resources/products/alerts/potential-data-integrity-issues-sep-2024</link>
      <guid>https://mongodbcom.website.prod.corp.mongodb.com/resources/products/alerts/potential-data-integrity-issues-sep-2024</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine bug in MongoDB running on ARM64 or POWER architectures may store documents or index entries out of order, leading to inconsistencies and improperly sorted or incomplete query results.</p>
]]></description>
      <pubDate>Tue, 14 Mar 2023 18:51:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-10461</link>
      <guid>https://jira.mongodb.org/browse/WT-10461</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A storage engine issue can cause inconsistent incremental Ops Manager and Cloud Manager backups. Clusters restored from affected incremental backups can crash with checksum errors. Atlas customers/backups are not affected.</p>
]]></description>
      <pubDate>Tue, 23 May 2023 14:40:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/WT-10551</link>
      <guid>https://jira.mongodb.org/browse/WT-10551</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A race condition in mongosync 1.5 can lead to some writes on the source not being replicated to the destination. Upgrade to version 1.6 or later.</p>
]]></description>
      <pubDate>Fri, 10 Nov 2023 18:11:00 GMT</pubDate>
      <link>https://www.mongodb.com/docs/cluster-to-cluster-sync/current/release-notes/1.6/#other-notes</link>
      <guid>https://www.mongodb.com/docs/cluster-to-cluster-sync/current/release-notes/1.6/#other-notes</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>An issue affecting inserts to Sharded Time Series collections can result in inserted documents on these collections to be immediately orphaned, leading to documents not being returned by queries and potential data loss.</p>
]]></description>
      <pubDate>Wed, 29 Nov 2023 18:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-80203</link>
      <guid>https://jira.mongodb.org/browse/SERVER-80203</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>An issue in mongodump can cause keys in collection options to be dumped in the wrong order. These alterations could change the result set returned by a view or change which documents are accepted by a validator.</p>
]]></description>
      <pubDate>Tue, 20 Feb 2024 14:40:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/TOOLS-3411</link>
      <guid>https://jira.mongodb.org/browse/TOOLS-3411</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Issues affecting multi-document transactions on sharded clusters which can cause sharded multi-document transactions to return incorrect data and possibly miss writes.</p>
]]></description>
      <pubDate>Mon, 15 Apr 2024 18:43:00 GMT</pubDate>
      <link>https://www.mongodb.com/resources/products/alerts/critical-alert-sharding-txn-issues-apr-2024</link>
      <guid>https://www.mongodb.com/resources/products/alerts/critical-alert-sharding-txn-issues-apr-2024</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>&quot;Issues during the initial data copy in mongosync 1.1.0  1.7.1 may lead to some writes or documents on the source not being replicated to the destination. Upgrade to mongosync version 1.7.2 or later. Atlas Live Migrate relies on mongosync for migrations to MongoDB 6.0+ and the fix has been applied to Atlas Live Migrate.&quot;</p>
]]></description>
      <pubDate>Tue, 02 Jul 2024 14:07:00 GMT</pubDate>
      <link>https://www.mongodb.com/docs/cluster-to-cluster-sync/current/release-notes/1.7/</link>
      <guid>https://www.mongodb.com/docs/cluster-to-cluster-sync/current/release-notes/1.7/</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>To balance load and maintain a high quality of service, the Atlas Serverless system occasionally migrates data of serverless instances between different database servers. Certain multi-write, non-transactional database commands are not safely auto-retried by Atlas Serverless upon migration completion, which can lead to incorrect updates and deletes behavior.</p>
]]></description>
      <pubDate>Thu, 15 Aug 2024 19:35:00 GMT</pubDate>
      <link>https://mongodbcom.website.prod.corp.mongodb.com/resources/products/alerts/critical-alert-data-integrity-aug-2024</link>
      <guid>https://mongodbcom.website.prod.corp.mongodb.com/resources/products/alerts/critical-alert-data-integrity-aug-2024</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>In sharded clusters, a unique index with a non-simple collation (e.g. case-insensitive) whose shard key  equals or is a strict prefix of the index key pattern does not enforce uniqueness across shards. Different shards can independently accept documents with byte-distinct but collation-equivalent values (e.g. &quot;YES&quot; and &quot;yes&quot;), silently breaking uniqueness guarantees. This requires two or more shards, a unique index with a non-simple collation, and the shard key equals or is a strict prefix of the index key pattern.</p>
]]></description>
      <pubDate>Thu, 14 May 2026 10:11:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-85346</link>
      <guid>https://jira.mongodb.org/browse/SERVER-85346</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>&quot;A bug can cause incorrect results or crashes when running certain aggregation pipelines containing $group and $lookup while on MongoDB Server version 6.0.17.&quot;</p>
]]></description>
      <pubDate>Thu, 03 Oct 2024 09:41:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-91570</link>
      <guid>https://jira.mongodb.org/browse/SERVER-91570</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Queries may return incomplete results when Time Series collections created prior to MongoDB 5.2 have been upgraded to MongoDB 6.0 or newer prior to those collections being cloned. Relatedly, Time Series collections on MongoDB Rapid Releases 7.1.0-7.3.3 that had their collection granularity changed via collMod while on those versions, may have also returned incomplete query results.</p>
]]></description>
      <pubDate>Thu, 24 Oct 2024 10:13:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-91194</link>
      <guid>https://jira.mongodb.org/browse/SERVER-91194</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>A reshardCollection operation on a cluster with at least two shards can potentially omit a collections catalog entry in a shards local catalog if a movePrimary operation had previously been issued on the same cluster. This impacts operations involving data migration that lookup the database cache namely movePrimary, reshardCollection, moveRange, and moveChunk.</p>
]]></description>
      <pubDate>Wed, 11 Dec 2024 16:15:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-86622</link>
      <guid>https://jira.mongodb.org/browse/SERVER-86622</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Performing a delete with a non-metadata filter on a time-series collection that is sharded on the time field may result in data loss.</p>
]]></description>
      <pubDate>Wed, 29 Jan 2025 15:39:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-94559</link>
      <guid>https://jira.mongodb.org/browse/SERVER-94559</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>Time Series collections may experience data loss when multiple documents are inserted concurrently with ordered: false and retryable writes are enabled.</p>
]]></description>
      <pubDate>Wed, 29 Jan 2025 15:38:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-95067</link>
      <guid>https://jira.mongodb.org/browse/SERVER-95067</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>In certain situations, a resharded collection may have had retryable writes repeated on its documents multiple times.</p>
]]></description>
      <pubDate>Mon, 03 Mar 2025 17:43:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-89529</link>
      <guid>https://jira.mongodb.org/browse/SERVER-89529</guid>
    </item>
    <item>
      <title></title>
      <description><![CDATA[<p>When enabling the useBigInt64 option (disabled by default) to deserialize a value through the bson JavaScript library (which is included in the MongoDB Node.js driver), negative Int64 values can be parsed as large positive values (greater than 9,223,372,036,854,775,807).</p>
]]></description>
      <pubDate>Wed, 19 Mar 2025 12:09:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/NODE-6764</link>
      <guid>https://jira.mongodb.org/browse/NODE-6764</guid>
    </item>
    <item>
      <title>User may trigger invariant when allowed to send commands directly to shards (CVE-2021-32037)</title>
      <description><![CDATA[<p>An authorized user may trigger an invariant which may result in denial of service or server exit if a relevant aggregation request is sent to a shard. Usually, the requests are sent via mongos and special privileges are required in order to know the address of the shards and to log in to the shards of an auth enabled environment.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Wed, 24 Nov 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-59071</link>
      <guid>https://jira.mongodb.org/browse/SERVER-59071</guid>
    </item>
    <item>
      <title>Specific replication command with malformed oplog entries can crash secondaries (CVE-2021-20330)</title>
      <description><![CDATA[<p>An attacker with basic CRUD permissions on a replicated collection can run the applyOps command with specially malformed oplog entries, resulting in a potential denial of service on secondaries. This issue affects MongoDB Server v4.0 versions prior to 4.0.25; MongoDB Server v4.2 versions prior to 4.2.14; MongoDB Server v4.4 versions prior to 4.4.6.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Wed, 15 Dec 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-36263</link>
      <guid>https://jira.mongodb.org/browse/SERVER-36263</guid>
    </item>
    <item>
      <title>MongoDB Extension for VS Code may unexpectedly store credentials locally in clear text (CVE-2021-32039)</title>
      <description><![CDATA[<p>Users with appropriate file access may be able to access unencrypted user credentials saved by MongoDB Extension for VS Code in a binary file. These credentials may be used by malicious attackers to perform unauthorized actions. This vulnerability affects all MongoDB Extension for VS Code including and prior to version 0.7.0</p>
 <br> CVSS Score has been rated as 5.5]]></description>
      <pubDate>Thu, 20 Jan 2022 00:00:00 GMT</pubDate>
      <link>https://github.com/mongodb-js/vscode/releases/tag/v0.8.0</link>
      <guid>https://github.com/mongodb-js/vscode/releases/tag/v0.8.0</guid>
    </item>
    <item>
      <title>Denial of Service and Data Integrity vulnerability in features command (CVE-2021-32036)</title>
      <description><![CDATA[<p>An authenticated user without any specific authorizations may be able to repeatedly invoke the features command where at a high volume may lead to resource depletion or generate high lock contention. This may result in denial of service and in rare cases could result in id field collisions.</p>
 <br> CVSS Score has been rated as 5.4]]></description>
      <pubDate>Fri, 04 Feb 2022 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-59294</link>
      <guid>https://jira.mongodb.org/browse/SERVER-59294</guid>
    </item>
    <item>
      <title>Large aggregation pipelines with a specific stage can crash mongod under default configuration (CVE-2021-32040)</title>
      <description><![CDATA[<p>It may be possible to have an extremely long aggregation pipeline in conjunction with a specific stage/operator and cause a stack overflow due to the size of the stack frames used by that stage. If an attacker could cause such an aggregation to occur, they could maliciously crash MongoDB in a DoS attack. This vulnerability affects MongoDB versions prior to 5.0.4, 4.4.11, 4.2.16.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Tue, 12 Apr 2022 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-58203</link>
      <guid>https://jira.mongodb.org/browse/SERVER-58203</guid>
    </item>
    <item>
      <title>MongoDB Server (mongod) may crash in response to unexpected requests (CVE-2022-24272)</title>
      <description><![CDATA[<p>An authenticated user may trigger an invariant assertion during command dispatch due to incorrect validation on the $external database. This may result in mongod denial of service or server crash. This issue affects: MongoDB Inc. MongoDB Server v5.0 versions, prior to and including v5.0.6.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Wed, 11 May 2022 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-63968</link>
      <guid>https://jira.mongodb.org/browse/SERVER-63968</guid>
    </item>
    <item>
      <title>MongoDB Ops Manager may disclose sensitive information in Diagnostic Archive (CVE-2023-0342)</title>
      <description><![CDATA[<p>MongoDB Ops Manager Diagnostics Archive may not redact sensitive PEM key file password app settings. Archives do not include the PEM files themselves. This issue affects MongoDB Ops Manager v5.0 prior to 5.0.21 and MongoDB Ops Manager v6.0 prior to 6.0.12</p>
 <br> CVSS Score has been rated as 3.1]]></description>
      <pubDate>Fri, 09 Jun 2023 11:00:00 GMT</pubDate>
      <link>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-6-0-12</link>
      <guid>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-6-0-12</guid>
    </item>
    <item>
      <title>Deserializing compromised object with MongoDB .NET/C# Driver may cause remote code execution (CVE-2022-48282)</title>
      <description><![CDATA[<p>Under very specific circumstances (see Required configuration section below), a privileged user is able to cause arbitrary code to be executed which may cause further disruption to services. This is specific to applications written in C#. This affects all MongoDB .NET/C# Driver versions prior to and including v2.18.0Following configuration must be true for the vulnerability to be applicable:  *  Application must written in C# taking arbitrary data from users and serializing data using _t without any validation AND  *  Application must be running on a Windows host using the full .NET Framework, not .NET Core AND  *  Application must have domain model class with a property/field explicitly of type System.Object or a collection of type System.Object (against MongoDB best practice) AND  *  Malicious attacker must have unrestricted insert access to target database to add a _t discriminator.&quot;Following configuration must be true for the vulnerability to be applicable</p>
 <br> CVSS Score has been rated as 6.6]]></description>
      <pubDate>Tue, 21 Feb 2023 19:39:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CSHARP-4475</link>
      <guid>https://jira.mongodb.org/browse/CSHARP-4475</guid>
    </item>
    <item>
      <title>Privilege Escalation for Project Owner and Project User Admin Roles in Ops Manager (CVE-2023-4009)</title>
      <description><![CDATA[<p>In MongoDB Ops Manager v5.0 prior to 5.0.22 and v6.0 prior to 6.0.17 it is possible for an authenticated user with project owner or project user admin access to generate an API key with the privileges of org owner resulting in privilege escalation.</p>
 <br> CVSS Score has been rated as 7.2]]></description>
      <pubDate>Tue, 08 Aug 2023 10:30:00 GMT</pubDate>
      <link>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-6-0</link>
      <guid>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-6-0</guid>
    </item>
    <item>
      <title>Certificate validation issue in MongoDB Server running on Windows or macOS (CVE-2023-1409)</title>
      <description><![CDATA[<p>If the MongoDB Server running on Windows or macOS is configured to use TLS with a specific set of configuration options that are already known to work securely in other platforms (e.g. Linux), it is possible that client certificate validation may not be in effect, potentially allowing client to establish a TLS connection with the server that supplies any certificate.This issue affect all MongoDB Server v6.3 versions, MongoDB Server v5.0 versions v5.0.0 to v5.0.14 and all MongoDB Server v4.4 versions.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Wed, 23 Aug 2023 16:18:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-73662</link>
      <guid>https://jira.mongodb.org/browse/SERVER-73662</guid>
    </item>
    <item>
      <title>Secret logging may occur in debug mode of Atlas Operator  (CVE-2023-0436)</title>
      <description><![CDATA[<p>The affected versions of MongoDB Atlas Kubernetes Operator may print sensitive information like GCP service account keys and API integration secrets while DEBUG mode logging is enabled. This issue affects MongoDB Atlas Kubernetes Operator versions: 1.5.0, 1.6.0, 1.6.1, 1.7.0.Please note that this is reported on an EOL version of the product, and users are advised to upgrade to the latest supported version.Required Configuration:DEBUG logging is not enabled by default, and must be configured by the end-user. To check the log-level of the Operator, review the flags passed in your deployment configuration (eg.  <a href="https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27">https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27</a> <a href="https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27">https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27</a> )</p>
 <br> CVSS Score has been rated as 4.5]]></description>
      <pubDate>Tue, 07 Nov 2023 12:41:00 GMT</pubDate>
      <link>https://github.com/mongodb/mongodb-atlas-kubernetes/releases/tag/v1.7.1</link>
      <guid>https://github.com/mongodb/mongodb-atlas-kubernetes/releases/tag/v1.7.1</guid>
    </item>
    <item>
      <title>MongoDB client C Driver may infinitely loop when validating certain BSON input data (CVE-2023-0437)</title>
      <description><![CDATA[<p>When calling bson_utf8_validateon some inputs a loop with an exit condition that cannot be reached may occur, i.e. an infinite loop. This issue affects All MongoDB C Driver versions prior to versions 1.25.0.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Fri, 12 Jan 2024 14:13:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-4747</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-4747</guid>
    </item>
    <item>
      <title>MongoDB Server may allow successful untrusted connection  (CVE-2024-1351)</title>
      <description><![CDATA[<p>Under certain configurations of --tlsCAFile and tls.CAFile, MongoDB Server may skip peer certificate validation which may result in untrusted connections to succeed. This may effectively reduce the security guarantees provided by TLS and open connections  that should have been closed due to failing certificate validation. This issue affects MongoDB Server v7.0 versions prior to and including 7.0.5, MongoDB Server v6.0 versions prior to and including 6.0.13, MongoDB Server v5.0 versions prior to and including 5.0.24 and MongoDB Server v4.4 versions prior to and including 4.4.28.Required Configuration : A server process will allow incoming connections to skip peer certificate validation if the server process was started with TLS enabled (net.tls.mode set to allowTLS, preferTLS, or requireTLS) and without a net.tls.CAFile configured.</p>
 <br> CVSS Score has been rated as 8.8]]></description>
      <pubDate>Thu, 07 Mar 2024 09:31:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-72839</link>
      <guid>https://jira.mongodb.org/browse/SERVER-72839</guid>
    </item>
    <item>
      <title>Some MongoDB Drivers may publish events containing authentication-related data to a command listener configured by an application (CVE-2021-32050)</title>
      <description><![CDATA[<p>Some MongoDB Drivers may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when specific authentication-related commands are executed.Without due care, an application may inadvertently expose this sensitive information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default).This issue affects the MongoDB C Driver 1.0.0 prior to 1.17.7, MongoDB PHP Driver 1.0.0 prior to 1.9.2, MongoDB Swift Driver 1.0.0 prior to 1.1.1, MongoDB Node.js Driver 3.6 prior to 3.6.10, MongoDB Node.js Driver 4.0 prior to 4.17.0 and MongoDB Node.js Driver 5.0 prior to 5.8.0. This issue also affects users of the MongoDB C++ Driver dependent on the C driver 1.0.0 prior to 1.17.7 (C++ driver prior to 3.7.0).</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Tue, 29 Aug 2023 15:24:30 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/PHPC-1869</link>
      <guid>https://jira.mongodb.org/browse/PHPC-1869</guid>
    </item>
    <item>
      <title>Kubernetes Operator generates potentially insecure certificates (CVE-2020-7922)</title>
      <description><![CDATA[<p>X.509 certificates generated by the MongoDB Enterprise Kubernetes Operator may allow an attacker with access to the Kubernetes cluster improper access to MongoDB instances. Customers who do not use X.509 authentication, and those who do not use the Operator to generate their X.509 certificates are unaffected. This issue affects: MongoDB Inc. MongoDB Enterprise Kubernetes Operator version 1.0, 1.1, 1.2 versions prior to 1.2.4, 1.3 versions prior to 1.3.1, 1.2, 1.4 versions prior to 1.4.4.</p>
 <br> CVSS Score has been rated as 6.4]]></description>
      <pubDate>Thu, 09 Apr 2020 00:00:00 GMT</pubDate>
      <link>https://github.com/mongodb/mongodb-enterprise-kubernetes/releases/tag/1.2.5</link>
      <guid>https://github.com/mongodb/mongodb-enterprise-kubernetes/releases/tag/1.2.5</guid>
    </item>
    <item>
      <title>MongoDB Server (mongod) may crash when generating ftdc (CVE-2024-3374)</title>
      <description><![CDATA[<p>An unauthenticated user can trigger a fatal assertion in the server while generating ftdc diagnostic metrics due to attempting to build a BSON object that exceeds certain memory sizes. This issue affects MongoDB Server v5.0 versions prior to and including 5.0.16 and MongoDB Server v6.0 versions prior to and including 6.0.5.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Tue, 14 May 2024 13:26:42 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-75601</link>
      <guid>https://jira.mongodb.org/browse/SERVER-75601</guid>
    </item>
    <item>
      <title>MongoDB Server may have unexpected application behaviour due to invalid BSON (CVE-2024-3372)</title>
      <description><![CDATA[<p>Improper validation of certain metadata input may result in the server not correctly serialising BSON. This can be performed pre-authentication and may cause unexpected application behavior including unavailability of serverStatus responses. This issue affects MongoDB Server v7.0 versions prior to 7.0.6, MongoDB Server v6.0 versions prior to 6.0.14 and MongoDB Server v.5.0 versions prior to 5.0.25.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Tue, 14 May 2024 13:24:05 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-85263</link>
      <guid>https://jira.mongodb.org/browse/SERVER-85263</guid>
    </item>
    <item>
      <title>Out-of-bounds read in bson module of PyMongo (CVE-2024-5629)</title>
      <description><![CDATA[<p>An out-of-bounds read in the &#39;bson&#39; module of PyMongo 4.6.2 or earlier allows deserialization of malformed BSON provided by a Server to raise an exception which may contain arbitrary application memory.</p>
 <br> CVSS Score has been rated as 4.7]]></description>
      <pubDate>Wed, 05 Jun 2024 14:32:56 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/PYTHON-4305</link>
      <guid>https://jira.mongodb.org/browse/PYTHON-4305</guid>
    </item>
    <item>
      <title>ejson shell parser in MongoDB Compass maybe bypassed (CVE-2024-6376)</title>
      <description><![CDATA[<p>MongoDB Compass may be susceptible to code injection due to insufficient sandbox protection settings with the usage of ejson shell parser in Compass&#39; connection handling. This issue affects MongoDB Compass versions prior to version 1.42.2</p>
 <br> CVSS Score has been rated as 7]]></description>
      <pubDate>Mon, 01 Jul 2024 14:57:31 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/COMPASS-7496</link>
      <guid>https://jira.mongodb.org/browse/COMPASS-7496</guid>
    </item>
    <item>
      <title>Missing authorization check may lead to shard key refinement (CVE-2024-6375)</title>
      <description><![CDATA[<p>A command for refining a collection shard key is missing an authorization check. This may cause the command to run directly on a shard, leading to either degradation of query performance, or to revealing chunk boundaries through timing side channels. This affects MongoDB Server v5.0 versions, prior to 5.0.22, MongoDB Server v6.0 versions, prior to 6.0.11 and MongoDB Server v7.0 versions prior to 7.0.3.</p>
 <br> CVSS Score has been rated as 5.4]]></description>
      <pubDate>Mon, 01 Jul 2024 14:40:32 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-79327</link>
      <guid>https://jira.mongodb.org/browse/SERVER-79327</guid>
    </item>
    <item>
      <title>MongoDB C Driver bson_strfreev may be susceptible to integer overflow (CVE-2024-6381)</title>
      <description><![CDATA[<p>The bson_strfreev function in the MongoDB C driver library may be susceptible to an integer overflow where the function will try to free memory at a negative offset. This may result in memory corruption. This issue affected libbson versions prior to 1.26.2</p>
 <br> CVSS Score has been rated as 4]]></description>
      <pubDate>Tue, 02 Jul 2024 17:14:48 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-5622</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-5622</guid>
    </item>
    <item>
      <title>Adversarial unsanitized input may cause MongoDB Rust Driver to issue unintended commands. (CVE-2024-6382)</title>
      <description><![CDATA[<p>Incorrect handling of certain string inputs may result in MongoDB Rust driver constructing unintended server commands. This may cause unexpected application behavior including data modification. This issue affects MongoDB Rust Driver 2.0 versions prior to 2.8.2</p>
 <br> CVSS Score has been rated as 6.4]]></description>
      <pubDate>Tue, 02 Jul 2024 17:17:50 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/RUST-1881</link>
      <guid>https://jira.mongodb.org/browse/RUST-1881</guid>
    </item>
    <item>
      <title>MongoDB C Driver bson_string_append may be vulnerable to a buffer overflow (CVE-2024-6383)</title>
      <description><![CDATA[<p>The bson_string_append function in MongoDB C Driver may be vulnerable to a buffer overflow where the function might attempt to allocate too small of buffer and may lead to memory corruption of neighbouring heap memory. This issue affects libbson versions prior to 1.27.1</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Wed, 03 Jul 2024 21:33:47 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-5628</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-5628</guid>
    </item>
    <item>
      <title>Accessing Untrusted Directory May Allow Local Privilege Escalation (CVE-2024-7553)</title>
      <description><![CDATA[<p>Incorrect validation of files loaded from a local untrusted directory may allow local privilege escalation if the underlying operating systems is Windows. This may result in the application executing arbitrary behaviour determined by the contents of untrusted files. This issue affects MongoDB Server v5.0 versions prior to 5.0.27, MongoDB Server v6.0 versions prior to 6.0.16, MongoDB Server v7.0 versions prior to 7.0.12, MongoDB Server v7.3 versions prior 7.3.3, MongoDB C Driver versions prior to 1.26.2 and MongoDB PHP Driver versions prior to 1.18.1.Required Configuration:Only environments with Windows as the underlying operating system is affected by this issue</p>
 <br> CVSS Score has been rated as 7.3]]></description>
      <pubDate>Wed, 07 Aug 2024 09:57:49 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/PHPC-2369</link>
      <guid>https://jira.mongodb.org/browse/PHPC-2369</guid>
    </item>
    <item>
      <title>Backup files may be downloaded by underprivileged users in MongoDB Enterprise Server (CVE-2024-6384)</title>
      <description><![CDATA[<p>&quot;Hot&quot; backup files may be downloaded by underprivileged users, if they are capable of acquiring a unique backup identifier. This issue affects MongoDB Enterprise Server v6.0 versions prior to 6.0.16, MongoDB Enterprise Server v7.0 versions prior to 7.0.11 and MongoDB Enterprise Server v7.3 versions prior to 7.3.3</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Tue, 13 Aug 2024 14:22:22 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-93516</link>
      <guid>https://jira.mongodb.org/browse/SERVER-93516</guid>
    </item>
    <item>
      <title>MongoDB Server binaries may load potentially insecure shared libraries from specific relative paths (CVE-2024-8207)</title>
      <description><![CDATA[<p>In certain highly specific configurations of the host system and MongoDB server binary installation on Linux Operating Systems, it may be possible for a unintended actor with host-level access to cause the MongoDB Server binary to load unintended actor-controlled shared libraries when the server binary is started, potentially resulting in the unintended actor gaining full control over the MongoDB server process. This issue affects MongoDB Server v5.0 versions prior to 5.0.14 and MongoDB Server v6.0 versions prior to 6.0.3.Required Configuration: Only environments with Linux as the underlying operating system is affected by this issue</p>
 <br> CVSS Score has been rated as 6.4]]></description>
      <pubDate>Tue, 27 Aug 2024 11:28:06 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-69507</link>
      <guid>https://jira.mongodb.org/browse/SERVER-69507</guid>
    </item>
    <item>
      <title>MongoDB Server may access non-initialized region of memory leading to unexpected behaviour (CVE-2024-8654)</title>
      <description><![CDATA[<p>MongoDB Server may access non-initialized region of memory leading to unexpected behaviour when zero arguments are called in internal aggregation stage. This issue affected MongoDB Server v6.0 version 6.0.3.</p>
 <br> CVSS Score has been rated as 5]]></description>
      <pubDate>Tue, 10 Sep 2024 13:35:50 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-71477</link>
      <guid>https://jira.mongodb.org/browse/SERVER-71477</guid>
    </item>
    <item>
      <title>MongoDB Server secondaries may crash due to forced index constraints (CVE-2024-8305)</title>
      <description><![CDATA[<p>prepareUnique index may cause secondaries to crash due to incorrect enforcement of index constraints on secondaries, where in extreme cases may cause multiple secondaries crashing leading to no primaries. This issue affects MongoDB Server v6.0 versions prior to 6.0.17, MongoDB Server v7.0 versions prior to 7.0.13 and MongoDB Server v7.3 versions prior to 7.3.4</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 21 Oct 2024 14:10:31 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-92382</link>
      <guid>https://jira.mongodb.org/browse/SERVER-92382</guid>
    </item>
    <item>
      <title>CSFLE and Queryable Encryption self-lookup may fail to encrypt values in subpipelines (CVE-2024-8013)</title>
      <description><![CDATA[<p>A bug in query analysis of certain complex self-referential $lookup subpipelines may result in literal values in expressions for encrypted fields to be sent to the server as plaintext instead of ciphertext. Should this occur, no documents would be returned or written. This issue affects mongocryptd binary (v5.0 versions prior to 5.0.29, v6.0 versions prior to 6.0.17, v7.0 versions prior to 7.0.12 and v7.3 versions prior to 7.3.4) and mongo_crypt_v1.so shared libraries (v6.0 versions prior to 6.0.17, v7.0 versions prior to 7.0.12 and v7.3 versions prior to 7.3.4) released alongside MongoDB Enterprise Server versions.</p>
 <br> CVSS Score has been rated as 2.2]]></description>
      <pubDate>Mon, 28 Oct 2024 12:58:05 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-96254</link>
      <guid>https://jira.mongodb.org/browse/SERVER-96254</guid>
    </item>
    <item>
      <title>Improper neutralization of null bytes may lead to buffer over-reads in MongoDB Server (CVE-2024-10921)</title>
      <description><![CDATA[<p>An authorized user may trigger crashes or receive the contents of buffer over-reads of Server memory by issuing specially crafted requests that construct malformed BSON in the MongoDB Server. This issue affects MongoDB Server v5.0 versions prior to 5.0.30 , MongoDB Server v6.0 versions prior to 6.0.19, MongoDB Server v7.0 versions prior to 7.0.15 and MongoDB Server v8.0 versions prior to and including 8.0.2.</p>
 <br> CVSS Score has been rated as 6.8]]></description>
      <pubDate>Thu, 14 Nov 2024 16:04:04 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-96419</link>
      <guid>https://jira.mongodb.org/browse/SERVER-96419</guid>
    </item>
    <item>
      <title>Insufficient validation of external input in Compass may enable MITM attacks (CVE-2024-3371)</title>
      <description><![CDATA[<p>MongoDB Compass may accept and use insufficiently validated input from an untrusted external source. This may cause unintended application behavior, including data disclosure and enabling attackers to impersonate users. This issue affects MongoDB Compass versions 1.35.0 to 1.42.0.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Wed, 24 Apr 2024 16:32:07 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/COMPASS-7260</link>
      <guid>https://jira.mongodb.org/browse/COMPASS-7260</guid>
    </item>
    <item>
      <title>Administrative action may disable enforcement of per-user IP whitelisting (CVE-2020-7921)</title>
      <description><![CDATA[<p>Improper serialization of internal state in the authorization subsystem in MongoDB Server&#39;s authorization subsystem permits a user with valid credentials to bypass IP whitelisting protection mechanisms following administrative action. This issue affects: MongoDB Inc. MongoDB Server 4.2 versions prior to 4.2.3; 4.0 versions prior to 4.0.15; 4.3 versions prior to 4.3.3; 3.6 versions prior to 3.6.18.</p>
 <br> CVSS Score has been rated as 4.6]]></description>
      <pubDate>Wed, 06 May 2020 11:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-45472</link>
      <guid>https://jira.mongodb.org/browse/SERVER-45472</guid>
    </item>
    <item>
      <title>Process termination via PID file manipulation (CVE-2019-2389)</title>
      <description><![CDATA[<p>Incorrect scoping of kill operations in MongoDB Server&#39;s packaged SysV init scripts allow users with write access to the PID file to insert arbitrary PIDs to be killed when the root user stops the MongoDB process via SysV init. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.11; v3.6 versions prior to 3.6.14; v3.4 versions prior to 3.4.22.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Fri, 30 Aug 2019 11:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-40563</link>
      <guid>https://jira.mongodb.org/browse/SERVER-40563</guid>
    </item>
    <item>
      <title>Potential exposure of log information in Ops Manager (CVE-2019-2388)</title>
      <description><![CDATA[<p>In affected Ops Manager versions there is an exposed http route was that may allow attackers to view a specific access log of a publicly exposed Ops Manager instance. This issue affects: MongoDB Inc. MongoDB Ops Manager 4.0 versions 4.0.9, 4.0.10 and MongoDB Ops Manager 4.1 version 4.1.5.</p>
 <br> CVSS Score has been rated as 5.8]]></description>
      <pubDate>Wed, 13 May 2020 11:00:00 GMT</pubDate>
      <link>https://docs.opsmanager.mongodb.com/current/release-notes/application/#onprem-server-4-0</link>
      <guid>https://docs.opsmanager.mongodb.com/current/release-notes/application/#onprem-server-4-0</guid>
    </item>
    <item>
      <title>JS-bson may incorrectly serialise some requests (CVE-2019-2391)</title>
      <description><![CDATA[<p>Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure. This issue affects: MongoDB Inc. js-bson library version 1.1.3 and prior to.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Tue, 31 Mar 2020 11:00:00 GMT</pubDate>
      <link>https://github.com/mongodb/js-bson/releases/tag/v1.1.4</link>
      <guid>https://github.com/mongodb/js-bson/releases/tag/v1.1.4</guid>
    </item>
    <item>
      <title>Authorization session conflation (CVE-2019-2386)</title>
      <description><![CDATA[<p>After user deletion in MongoDB Server the improper invalidation of authorization sessions allows an authenticated user&#39;s session to persist and become conflated with new accounts, if those accounts reuse the names of deleted ones. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.9; v3.6 versions prior to 3.6.13; v3.4 versions prior to 3.4.22.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 06 Aug 2019 11:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-38984</link>
      <guid>https://jira.mongodb.org/browse/SERVER-38984</guid>
    </item>
    <item>
      <title>Code execution on Windows via OpenSSL engine injection (CVE-2019-2390)</title>
      <description><![CDATA[<p>An unprivileged user or program on Microsoft Windows which can create OpenSSL configuration files in a fixed location may cause utility programs shipped with MongoDB server to run attacker defined code as the user running the utility. This issue affects: MongoDB Inc. MongoDB Server 4.0 prior to 4.0.11; 3.6 prior to 3.6.14; 3.4 prior to 3.4.22.</p>
 <br> CVSS Score has been rated as 8.2]]></description>
      <pubDate>Fri, 30 Aug 2019 11:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-42233</link>
      <guid>https://jira.mongodb.org/browse/SERVER-42233</guid>
    </item>
    <item>
      <title>Specific GeoQuery can cause DoS against MongoDB Server (CVE-2020-7923)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may cause denial of service by issuing specially crafted queries, which violate an invariant in the query subsystem&#39;s support for geoNear. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.0-rc7; v4.2 versions prior to 4.2.8; v4.0 versions prior to 4.0.19.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 21 Aug 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-47773</link>
      <guid>https://jira.mongodb.org/browse/SERVER-47773</guid>
    </item>
    <item>
      <title>Denial of Service when processing malformed Role names (CVE-2020-7925)</title>
      <description><![CDATA[<p>Incorrect validation of user input in the role name parser may lead to use of uninitialized memory allowing an unauthenticated attacker to use a specially crafted request to cause a denial of service. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.0-rc12; v4.2 versions prior to 4.2.9.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-49142</link>
      <guid>https://jira.mongodb.org/browse/SERVER-49142</guid>
    </item>
    <item>
      <title>Specific query can cause a DoS against MongoDB Server (CVE-2020-7926)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may cause denial of service by issuing a specially crafted query which violates an invariant in the server selection subsystem. This issue affects: MongoDB Server version 4.4 prior to 4.4.1. Versions before 4.4 are not affected.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-50170</link>
      <guid>https://jira.mongodb.org/browse/SERVER-50170</guid>
    </item>
    <item>
      <title>Potential privilege escalation in Ops Manager API (CVE-2020-7927)</title>
      <description><![CDATA[<p>Specially crafted API calls may allow an authenticated user who holds Organization Owner privilege to obtain an API key with Global Role privilege. This issue affects MongoDB Ops Manager v4.2 versions 4.2.0-4.2.17, v4.3 versions 4.3.0-4.3.9 and v4.4 versions 4.4.0-4.4.2.</p>
 <br> CVSS Score has been rated as 8.1]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://docs.opsmanager.mongodb.com/current/release-notes/application/#onprem-server-4-4-3</link>
      <guid>https://docs.opsmanager.mongodb.com/current/release-notes/application/#onprem-server-4-4-3</guid>
    </item>
    <item>
      <title>$mod can result in UB (CVE-2019-2392)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which use the $mod operator to overflow negative values. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.1; v4.2 versions prior to 4.2.9; v4.0 versions prior to 4.0.20; v3.6 versions prior to 3.6.20.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-43699</link>
      <guid>https://jira.mongodb.org/browse/SERVER-43699</guid>
    </item>
    <item>
      <title>Crash while joining collections with $lookup (CVE-2019-2393)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which use $lookup and collations. This issue affects: MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0 versions prior to 4.0.13; v3.6 versions prior to 3.6.15.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-43350</link>
      <guid>https://jira.mongodb.org/browse/SERVER-43350</guid>
    </item>
    <item>
      <title>Crash while handling internal Javascript exception types (CVE-2019-20923)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which throw unhandled Javascript exceptions containing types intended to be scoped to the Javascript engine&#39;s internals. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.7.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-39481</link>
      <guid>https://jira.mongodb.org/browse/SERVER-39481</guid>
    </item>
    <item>
      <title> Invariant in IndexBoundsBuilder (CVE-2019-20924)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries which trigger an invariant in the IndexBoundsBuilder. This issue affects: MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.2.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Tue, 01 Dec 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-44377</link>
      <guid>https://jira.mongodb.org/browse/SERVER-44377</guid>
    </item>
    <item>
      <title>Improper neutralization of null byte leads to read overrun (CVE-2020-7928)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger a read overrun and access arbitrary memory by issuing specially crafted queries. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.1; v4.2 versions prior to 4.2.9; v4.0 versions prior to 4.0.20; v3.6 versions prior to 3.6.20.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 23 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-49404</link>
      <guid>https://jira.mongodb.org/browse/SERVER-49404</guid>
    </item>
    <item>
      <title>MongoDB Rust Driver may publish events containing authentication-related data to a connection pool event listener configured by an application (CVE-2021-20332)</title>
      <description><![CDATA[<p>Specific MongoDB Rust Driver versions can include credentials used by the connection pool to authenticate connections in the monitoring event that is emitted when the pool is created. The user&#39;s logging infrastructure could then potentially ingest these events and unexpectedly leak the credentials. Note that such monitoring is not enabled by default.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Mon, 02 Aug 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/RUST-591</link>
      <guid>https://jira.mongodb.org/browse/RUST-591</guid>
    </item>
    <item>
      <title>Invariant failure in applyOps (CVE-2018-20804)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted applyOps invocations. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.10; v3.6 versions prior to 3.6.13.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-35636</link>
      <guid>https://jira.mongodb.org/browse/SERVER-35636</guid>
    </item>
    <item>
      <title>Invariant with $elemMatch (CVE-2018-20805)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which perform an $elemMatch This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.5; v3.6 versions prior to 3.6.10. This issue affects: MongoDB Inc. MongoDB Server 3.6 versions prior to 3.6.10; 4.0 versions prior to 4.0.5.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-38164</link>
      <guid>https://jira.mongodb.org/browse/SERVER-38164</guid>
    </item>
    <item>
      <title>Denial of service via malformed network packet (CVE-2019-20925)</title>
      <description><![CDATA[<p>An unauthenticated client can trigger denial of service by issuing specially crafted wire protocol messages, which cause the message decompressor to incorrectly allocate memory. This issue affects: MongoDB Inc. MongoDB Server v4.2 versions prior to 4.2.1; v4.0 versions prior to 4.0.13; v3.6 versions prior to 3.6.15; v3.4 versions prior to 3.4.24.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Tue, 24 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-43751</link>
      <guid>https://jira.mongodb.org/browse/SERVER-43751</guid>
    </item>
    <item>
      <title>Infinite loop in aggregation expression (CVE-2018-20803)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries, which loop indefinitely in mathematics processing while retaining locks. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.5; v3.6 versions prior to 3.6.10; v3.4 versions prior to 3.4.19.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 23 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-38070</link>
      <guid>https://jira.mongodb.org/browse/SERVER-38070</guid>
    </item>
    <item>
      <title>SSL may be unexpectedly disabled during upgrade of multiple-server MongoDB Ops Manager (CVE-2021-20335)</title>
      <description><![CDATA[<p>For MongoDB Ops Manager &lt;= 4.2.24 with multiple OM application servers, that have SSL turned on for their MongoDB processes, the upgrade to MongoDB Ops Manager &lt;= 4.4.12 triggers a bug where Automation thinks SSL is being turned off, and can disable SSL temporarily for members of the cluster. This issue is temporary and eventually corrects itself after MongoDB Ops Manager instances have finished upgrading to MongoDB Ops Manager 4.4. In addition, customers must be running with clientCertificateMode=OPTIONAL / allowConnectionsWithoutCertificates=true to be impacted*.* Customers upgrading from Ops Manager 4.2.X to 4.2.24 and finally to Ops Manager 4.4.13+ are unaffected by this issue.</p>
 <br> CVSS Score has been rated as 6.7]]></description>
      <pubDate>Thu, 11 Feb 2021 00:00:00 GMT</pubDate>
      <link>https://docs.opsmanager.mongodb.com/v4.2/release-notes/application/#onprem-server-4-2-23</link>
      <guid>https://docs.opsmanager.mongodb.com/v4.2/release-notes/application/#onprem-server-4-2-23</guid>
    </item>
    <item>
      <title> MongoDB Node.js client side field level encryption library may not be validating KMS certificate (CVE-2021-20327)</title>
      <description><![CDATA[<p>A specific version of the Node.js mongodb-client-encryption module does not perform correct validation of the KMS servers certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Node.js driver and the KMS service rendering client-side field level encryption (CSFLE) ineffective. This issue was discovered during internal testing and affects mongodb-client-encryption module version 1.2.0, which was available from 2021-Jan-29 and deprecated in the NPM Registry on 2021-Feb-04. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services from applications residing inside the AWS, GCP, and Azure nework fabrics due to compensating controls in these environments. This issue does not impact driver workloads that dont use Field Level Encryption.</p>
 <br> CVSS Score has been rated as 6.4]]></description>
      <pubDate>Thu, 25 Feb 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/NODE-3125</link>
      <guid>https://jira.mongodb.org/browse/NODE-3125</guid>
    </item>
    <item>
      <title> MongoDB Java driver client-side field level encryption not verifying KMS host name (CVE-2021-20328)</title>
      <description><![CDATA[<p>Specific versions of the Java driver that support client-side field level encryption (CSFLE) fail to perform correct host name verification on the KMS servers certificate. This vulnerability in combination with a privileged network position active MITM attack could result in interception of traffic between the Java driver and the KMS service rendering Field Level Encryption ineffective. This issue was discovered during internal testing and affects all versions of the Java driver that support CSFLE. The Java async, Scala, and reactive streams drivers are not impacted. This vulnerability does not impact driver traffic payloads with CSFLE-supported key services originating from applications residing inside the AWS, GCP, and Azure network fabrics due to compensating controls in these environments. This issue does not impact driver workloads that dont use Field Level Encryption.</p>
 <br> CVSS Score has been rated as 6.4]]></description>
      <pubDate>Thu, 25 Feb 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/JAVA-4017</link>
      <guid>https://jira.mongodb.org/browse/JAVA-4017</guid>
    </item>
    <item>
      <title>Specially crafted regex query can cause DoS (CVE-2020-7929)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted query contain a type of regex. This issue affects: MongoDB Inc. MongoDB Server v3.6 versions prior to 3.6.21 and MongoDB Server v4.0 versions prior to 4.0.20.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 26 Feb 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-51083</link>
      <guid>https://jira.mongodb.org/browse/SERVER-51083</guid>
    </item>
    <item>
      <title>Invariant failure when explaining a find with a UUID (CVE-2018-25004)</title>
      <description><![CDATA[<p>A user authorized to performing a specific type of query may trigger a denial of service by issuing a generic explain command on a find query. This issue affects: MongoDB Inc. MongoDB Server v4.0 versions prior to 4.0.6; MongoDB Server v3.6 versions prior to 3.6.11.</p>
 <br> CVSS Score has been rated as 4.9]]></description>
      <pubDate>Fri, 26 Feb 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-38275</link>
      <guid>https://jira.mongodb.org/browse/SERVER-38275</guid>
    </item>
    <item>
      <title>Local privilege escalation in MongoDB Compass for Windows (CVE-2021-20334)</title>
      <description><![CDATA[<p>A malicious 3rd party with local access to the Windows machine where MongoDB Compass is installed can execute arbitrary software with the privileges of the user who is running MongoDB Compass. This issue affects: MongoDB Inc. MongoDB Compass 1.x version 1.3.0 on Windows and later versions; 1.x versions prior to 1.25.0 on Windows.</p>
 <br> CVSS Score has been rated as 4.8]]></description>
      <pubDate>Tue, 06 Apr 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/COMPASS-4510</link>
      <guid>https://jira.mongodb.org/browse/COMPASS-4510</guid>
    </item>
    <item>
      <title>Specific command line parameter might result in accepting invalid certificate (CVE-2020-7924)</title>
      <description><![CDATA[<p>Usage of specific command line parameter in MongoDB Tools which was originally intended to just skip hostname checks, may result in MongoDB skipping all certificate validation. This may result in accepting invalid certificates.This issue affects: MongoDB Inc. MongoDB Database Tools 3.6 versions later than 3.6.5; 3.6 versions prior to 3.6.21; 4.0 versions prior to 4.0.21; 4.2 versions prior to 4.2.11; 100 versions prior to 100.2.0. MongoDB Inc. Mongomirror 0 versions later than 0.6.0.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Mon, 12 Apr 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/TOOLS-2587</link>
      <guid>https://jira.mongodb.org/browse/TOOLS-2587</guid>
    </item>
    <item>
      <title>Specially crafted query may result in a denial of service of mongod (CVE-2021-20326)</title>
      <description><![CDATA[<p>A user authorized to performing a specific type of find query may trigger a denial of service. This issue affects: MongoDB Inc. MongoDB Server v4.4 versions prior to 4.4.4.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 30 Apr 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-53929</link>
      <guid>https://jira.mongodb.org/browse/SERVER-53929</guid>
    </item>
    <item>
      <title>MongoDB C# Driver may publish events containing authentication-related data to a command listener configured by an application (CVE-2021-20331)</title>
      <description><![CDATA[<p>Specific versions of the MongoDB C# Driver may erroneously publish events containing authentication-related data to a command listener configured by an application. The published events may contain security-sensitive data when commands such as &quot;saslStart&quot;, &quot;saslContinue&quot;, &quot;isMaster&quot;, &quot;createUser&quot;, and &quot;updateUser&quot; are executed. Without due care, an application may inadvertently expose this authenticated-related information, e.g., by writing it to a log file. This issue only arises if an application enables the command listener feature (this is not enabled by default). This issue affects the MongoDB C# Driver 2.12 &lt;= 2.12.1.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Mon, 24 May 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CSHARP-3521</link>
      <guid>https://jira.mongodb.org/browse/CSHARP-3521</guid>
    </item>
    <item>
      <title>Specific cstrings input may not be properly validated in the Go Driver (CVE-2021-20329)</title>
      <description><![CDATA[<p>Specific cstrings input may not be properly validated in the MongoDB Go Driver when marshalling Go objects into BSON. A malicious user could use a Go object with specific string to potentially inject additional fields into marshalled documents. This issue affects all MongoDB GO Drivers up to (and including) 1.5.0.</p>
 <br> CVSS Score has been rated as 6.8]]></description>
      <pubDate>Thu, 10 Jun 2021 00:00:00 GMT</pubDate>
      <link>https://github.com/mongodb/mongo-go-driver/releases/tag/v1.5.1</link>
      <guid>https://github.com/mongodb/mongo-go-driver/releases/tag/v1.5.1</guid>
    </item>
    <item>
      <title>Server log entry spoofing via newline injection (CVE-2021-20333)</title>
      <description><![CDATA[<p>Sending specially crafted commands to a MongoDB Server may result in artificial log entries being generated or for log entries to be split. This issue affects MongoDB Server v3.6 versions prior to 3.6.20; MongoDB Server v4.0 versions prior to 4.0.21; MongoDB Server v4.2 versions prior to 4.2.10;</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Fri, 23 Jul 2021 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-50605</link>
      <guid>https://jira.mongodb.org/browse/SERVER-50605</guid>
    </item>
    <item>
      <title>Post-auth queries on compound index may crash mongod (CVE-2018-20802)</title>
      <description><![CDATA[<p>A user authorized to perform database queries may trigger denial of service by issuing specially crafted queries with compound indexes affecting QueryPlanner. This issue affects: MongoDB Inc. MongoDB Server v3.6 versions prior to 3.6.9, v4.0 versions prior to 4.0.3.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 30 Nov 2020 00:00:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-36993</link>
      <guid>https://jira.mongodb.org/browse/SERVER-36993</guid>
    </item>
    <item>
      <title>MongoDB may be susceptible to Invariant Failure due to batched delete (CVE-2025-13644)</title>
      <description><![CDATA[<p>MongoDB Server may experience an invariant failure during batched delete operations when handling documents. The issue arises when the server mistakenly assumes the presence of multiple documents in a batch based solely on document size exceeding BSONObjMaxSize. This issue affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.13, and MongoDB Server v8.1 versions prior to 8.1.2</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Tue, 25 Nov 2025 05:23:12 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-101180</link>
      <guid>https://jira.mongodb.org/browse/SERVER-101180</guid>
    </item>
    <item>
      <title>Cross-Shard Failovers May Lead to Partial Transaction Commit in MongoDB Server (CVE-2025-14345)</title>
      <description><![CDATA[<p>A post-authenticationflaw in the network two-phase commit protocol used for cross-shard transactions in MongoDB Server may lead to logical data inconsistencies under specific conditions which are not predictable and exist for a very short period of time. This error can cause the transaction coordination logic to misinterpret the transaction as committed, resulting in inconsistent state on those shards. This may lead to low integrity and availability impact.This issue impacts MongoDB Server v8.0 versions prior to 8.0.16, MongoDB Server v7.0 versions prior to 7.0.26 and MongoDB server v8.2 versions prior to 8.2.2.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Tue, 09 Dec 2025 15:00:38 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106075</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106075#2</guid>
    </item>
    <item>
      <title>Zlib compressed protocol header length confusion may allow memory read (CVE-2025-14847)</title>
      <description><![CDATA[<p>Mismatched length fields in Zlib compressed protocol headers may allow a read of uninitialized heap memory by an unauthenticated client. This issue affects all MongoDB Server v7.0 prior to 7.0.28 versions, MongoDB Server v8.0 versions prior to 8.0.17, MongoDB Server v8.2 versions prior to 8.2.3, MongoDB Server v6.0 versions prior to 6.0.27, MongoDB Server v5.0 versions prior to 5.0.32, MongoDB Server v4.4 versions prior to 4.4.30, MongoDB Server v4.2 versions greater than or equal to 4.2.0, MongoDB Server v4.0 versions greater than or equal to 4.0.0, and MongoDB Server v3.6 versions greater than or equal to 3.6.0.</p>
 <br> CVSS Score has been rated as 8.7]]></description>
      <pubDate>Fri, 19 Dec 2025 11:00:22 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-115508</link>
      <guid>https://jira.mongodb.org/browse/SERVER-115508</guid>
    </item>
    <item>
      <title>Heap Out-of-Bounds Read in Go Driver GSSAPI C Wrappers enables application crash or information leak (CVE-2026-2303)</title>
      <description><![CDATA[<p>The mongo-go-driver repositorycontains CGo bindings for GSSAPI (Kerberos) authentication on Linux and macOS. The C wrapper implementation contains a heap out-of-bounds read vulnerability due to incorrect assumptions about string termination in the GSSAPI standard. Since GSSAPI buffers are not guaranteed to be null-terminated or have extra padding, this results in reading one byte past the allocated heap buffer.</p>
 <br> CVSS Score has been rated as 6.9]]></description>
      <pubDate>Tue, 10 Feb 2026 19:03:06 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/GODRIVER-3770</link>
      <guid>https://jira.mongodb.org/browse/GODRIVER-3770</guid>
    </item>
    <item>
      <title>Unsafe Reflection in Mongoid::Criteria.from_hash (CVE-2026-2302)</title>
      <description><![CDATA[<p>Under specific conditions when processing a maliciously crafted value of type Hash r, Mongoid::Criteria.from_hash may allow for executing arbitrary Ruby code.</p>
 <br> CVSS Score has been rated as 6.9]]></description>
      <pubDate>Tue, 10 Feb 2026 18:59:23 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOID-5919</link>
      <guid>https://jira.mongodb.org/browse/MONGOID-5919</guid>
    </item>
    <item>
      <title>Pre-Authentication Memory Exhaustion Denial of Service in MongoDB Server (CVE-2026-25611)</title>
      <description><![CDATA[<p>A series of specifically crafted, unauthenticated messages can exhaust available memory and crash a MongoDB server.</p>
 <br> CVSS Score has been rated as 8.7]]></description>
      <pubDate>Tue, 10 Feb 2026 17:52:47 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-116210</link>
      <guid>https://jira.mongodb.org/browse/SERVER-116210</guid>
    </item>
    <item>
      <title>Internal ResourceId collision may affect unrelated collections (CVE-2026-25612)</title>
      <description><![CDATA[<p>The internal locking mechanism of the MongoDB server uses an internal encoding of the resources in order to choose what lock to take. Collections may inadvertently collide with one another in this representation causing unavailability between them due to conflicting locks.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:05:23 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-114838</link>
      <guid>https://jira.mongodb.org/browse/SERVER-114838</guid>
    </item>
    <item>
      <title>An unsafe cast in the MongoDB query planner can result in a segmentation fault. (CVE-2026-25613)</title>
      <description><![CDATA[<p>An authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:54:50 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-113685</link>
      <guid>https://jira.mongodb.org/browse/SERVER-113685</guid>
    </item>
    <item>
      <title>profile command may permit unauthorized configuration (CVE-2026-25609)</title>
      <description><![CDATA[<p>Incorrect validation of the profile command may result in the determination that a request altering the &#39;filter&#39; is read-only.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Tue, 10 Feb 2026 18:39:11 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-112952</link>
      <guid>https://jira.mongodb.org/browse/SERVER-112952</guid>
    </item>
    <item>
      <title>Invalid $geoNear index hint may cause server crash (CVE-2026-25610)</title>
      <description><![CDATA[<p>An authorized user may trigger a server crash by running a $geoNear pipeline with certain invalid index hints.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:30:40 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-99119</link>
      <guid>https://jira.mongodb.org/browse/SERVER-99119</guid>
    </item>
    <item>
      <title>An authorized user may disable the MongoDB server by issuing a certain type of complex query due to boolean expression simplification (CVE-2026-1850)</title>
      <description><![CDATA[<p>Complex queries can cause excessive memory usage in MongoDB Query Planner resulting in an Out-Of-Memory Crash.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:49:32 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-114126</link>
      <guid>https://jira.mongodb.org/browse/SERVER-114126</guid>
    </item>
    <item>
      <title>Mongod can run out of stack memory when expressions create deeply nested documents (CVE-2026-1849)</title>
      <description><![CDATA[<p>MongoDB Server may experience an out-of-memory failure while evaluating expressions that produce deeply nested documents. The issue arises in recursive functions because the server does not periodically check the depth of the expression.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:52:52 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-102364</link>
      <guid>https://jira.mongodb.org/browse/SERVER-102364</guid>
    </item>
    <item>
      <title>Connections received from the proxy port may not count towards total accepted connections (CVE-2026-1848)</title>
      <description><![CDATA[<p>Connections received from the proxy port may not count towards total accepted connections, resulting in server crashes if the total number of connections exceeds available resources. This only applies to connections accepted from the proxy port, pending the proxy protocol header.</p>
 <br> CVSS Score has been rated as 8.2]]></description>
      <pubDate>Tue, 10 Feb 2026 18:22:41 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-114695</link>
      <guid>https://jira.mongodb.org/browse/SERVER-114695</guid>
    </item>
    <item>
      <title>MongoDB Server may crash when inserting large documents (CVE-2026-1847)</title>
      <description><![CDATA[<p>Inserting certain large documents into a replica set could lead to replica set secondaries not being able to fetch the oplog from the primary. This could stall replication inside the replica set leading to server crash.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 10 Feb 2026 18:16:24 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-113532</link>
      <guid>https://jira.mongodb.org/browse/SERVER-113532</guid>
    </item>
    <item>
      <title>MongoDB Shell may be susceptible to Control Character Injection via autocomplete (CVE-2025-1691)</title>
      <description><![CDATA[<p>The MongoDB Shell may be susceptible to control character injection where an attacker with control of the mongosh autocomplete feature, can use the autocompletion feature to input and run obfuscated malicious text. This requires user interaction in the form of the user using tab to autocomplete text that is a prefix of the attackers prepared autocompletion. This issue affects mongosh versions prior to2.3.9.The vulnerability is exploitable only when mongosh is connected to a cluster that is partially or fully controlled by an attacker.</p>
 <br> CVSS Score has been rated as 7.6]]></description>
      <pubDate>Thu, 27 Feb 2025 12:34:02 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOSH-2024</link>
      <guid>https://jira.mongodb.org/browse/MONGOSH-2024</guid>
    </item>
    <item>
      <title>Stack memory disclosure in filemd5 command (CVE-2026-4147)</title>
      <description><![CDATA[<p>An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 17 Mar 2026 15:50:21 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-119317</link>
      <guid>https://jira.mongodb.org/browse/SERVER-119317</guid>
    </item>
    <item>
      <title>ExpressionContext use-after-free in classic engine $lookup and $graphLookup aggregation operators (CVE-2026-4148)</title>
      <description><![CDATA[<p>A use-after-free vulnerability can be triggered in sharded clusters by an authenticated user with the read role who issues a specially crafted $lookup or $graphLookup aggregation pipeline.</p>
 <br> CVSS Score has been rated as 8.7]]></description>
      <pubDate>Tue, 17 Mar 2026 15:53:57 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-119319</link>
      <guid>https://jira.mongodb.org/browse/SERVER-119319</guid>
    </item>
    <item>
      <title>Memory safety issues in slot-based execution hash table spill (CVE-2026-4358)</title>
      <description><![CDATA[<p>A specially crafted aggregation query with $lookup by an authenticated user with write privileges can cause a double-free or use-after-free memory issue in the slot-based execution (SBE) engine when an in-memory hash table is spilled to disk.</p>
 <br> CVSS Score has been rated as 6.1]]></description>
      <pubDate>Tue, 17 Mar 2026 19:00:07 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-118849</link>
      <guid>https://jira.mongodb.org/browse/SERVER-118849</guid>
    </item>
    <item>
      <title>Heap-buffer-over-read in _mongoc_http_send via strstr on non-null-terminated buffer (CVE-2026-4359)</title>
      <description><![CDATA[<p>A compromised third party cloud server or man-in-the-middle attacker could send a malformed HTTP response and cause a crash in applications using the MongoDB C driver.</p>
 <br> CVSS Score has been rated as 2]]></description>
      <pubDate>Tue, 17 Mar 2026 19:42:03 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-6251</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-6251</guid>
    </item>
    <item>
      <title>MD5 checksum creation may cause availability loss (CVE-2026-6914)</title>
      <description><![CDATA[<p>Computing the MD5 checksum of a malformed BSON object under specific conditions may cause loss of availability in MongoDB server.This issue affects all MongoDB Server v8.2 versions, all MongoDB Server v8.1 versions, MongoDB Server v8.0 versions prior to 8.0.21, MongoDB Server v7.0 versions prior to 7.0.32</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Wed, 29 Apr 2026 16:47:02 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-119981</link>
      <guid>https://jira.mongodb.org/browse/SERVER-119981</guid>
    </item>
    <item>
      <title>Users could trigger a crash of mongod primaries during promotion to sharded (CVE-2026-5170)</title>
      <description><![CDATA[<p>A user with access to the cluster with a limited set of privilege actions can trigger a crash of amongod process during the limited and unpredictable window when the cluster is being promoted from a replica set to a sharded cluster. This may cause a denial of service by taking down the primary of the replica set.This issue affects MongoDB Server v8.2 versions prior to 8.2.2, MongoDB Server v8.0 versions between 8.0.18, MongoDB Server v7.0 versions between 7.0.31.</p>
 <br> CVSS Score has been rated as 6]]></description>
      <pubDate>Mon, 30 Mar 2026 15:28:57 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-101758</link>
      <guid>https://jira.mongodb.org/browse/SERVER-101758</guid>
    </item>
    <item>
      <title>bson_validate may skip validation when processing certain inputs (CVE-2026-6231)</title>
      <description><![CDATA[<p>The bson_validate function may return early on specific inputs and incorrectly report success. This behavior could result in skipping validation for BSON data, allowing malformed or invalid UTF-8 sequences to bypass validation and be processed incorrectly. The issue may affect applications that rely on these functions to validate untrusted BSON data before further processing. This issue affects MongoDB C Driver versions prior to 1.30.5, MongoDB C Driver version 2.0.0 and MongoDB C Driver version 2.0.1</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Mon, 13 Apr 2026 15:31:55 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-6017</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-6017</guid>
    </item>
    <item>
      <title>Flaw in the updateUser Command May Allow Unauthorized Configuration Change (CVE-2026-6915)</title>
      <description><![CDATA[<p>An authorization flaw in the user management command could allow an authenticated user to make limited changes to authentication-related data associated with another user account. This could affect how authentication is performed for the impacted account.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Wed, 29 Apr 2026 16:51:01 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-119679</link>
      <guid>https://jira.mongodb.org/browse/SERVER-119679</guid>
    </item>
    <item>
      <title>Post-authentication CPU utilization DoS via $trim/$ltrim/$rtrim operators (CVE-2026-8202)</title>
      <description><![CDATA[<p>Using a densely populated chars mask and a large input string in the MongoDB aggregation operators $trim, $ltrim, and $rtrim, an authenticated user with aggregation permissions can pin CPU utilization at 100% for an extended period of time.This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Wed, 13 May 2026 00:19:41 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-120668</link>
      <guid>https://jira.mongodb.org/browse/SERVER-120668</guid>
    </item>
    <item>
      <title>Post-authentication use-after-free error in $_internalJsEmit and mapreduce commands (CVE-2026-8336)</title>
      <description><![CDATA[<p>After invoking $_internalJsEmit, which is not intended to be directly accessible, or mapreduce commands map function in a certain way, an authenticated user can subsequently crash mongod when the server-side JavaScript engine (through $where, $function, mapreduce reduce stage, etc.) is used also in a specific way, resulting in a post-authentication denial-of-service.This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 7.7]]></description>
      <pubDate>Wed, 13 May 2026 00:16:16 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-121610</link>
      <guid>https://jira.mongodb.org/browse/SERVER-121610</guid>
    </item>
    <item>
      <title>Use-After-Free in MongoDB FLE Query Analysis When Processing Positional Projections on Encrypted Fields (CVE-2026-8201)</title>
      <description><![CDATA[<p>A use-after-free vulnerability exists in MongoDB&#39;s Field-Level Encryption (FLE) query analysis component, affecting client-side uses of mongocryptd and crypt_shared. Triggering this vulnerability requires control over the structure of a client&#39;s FLE-related query.This issue impacts MongoDB Servers mongocryptd component v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 6.1]]></description>
      <pubDate>Wed, 13 May 2026 00:12:35 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-122032</link>
      <guid>https://jira.mongodb.org/browse/SERVER-122032</guid>
    </item>
    <item>
      <title>Schema validation log messages may not redact user data (CVE-2026-8200)</title>
      <description><![CDATA[<p>When schema validation is enabled on a collection and an update or insert would violate the collection&#39;s schema, the local server log message generated may not have all user data redacted.This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 4.8]]></description>
      <pubDate>Wed, 13 May 2026 00:08:29 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-121895</link>
      <guid>https://jira.mongodb.org/browse/SERVER-121895</guid>
    </item>
    <item>
      <title>Post-auth memory exhaustion via bitwise match expressions (CVE-2026-8199)</title>
      <description><![CDATA[<p>An authenticated user can cause excess memory usage via bitwise match expression AST processing of $bitsAllSet, $bitsAnySet, $bitsAllClear, and $bitsAnyClear. This contributes to memory pressure and may lead to availability loss by OOM.This issue impacts MongoDB Server v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Wed, 13 May 2026 00:05:22 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-122449</link>
      <guid>https://jira.mongodb.org/browse/SERVER-122449</guid>
    </item>
    <item>
      <title>FlatBSON Duplicate Field Index Drift (CVE-2026-8053)</title>
      <description><![CDATA[<p>An issue in MongoDB Server&#39;s time-series collection implementation allows an authenticated user with database write privileges to trigger an out-of-bounds memory write in the mongod process. The issue results from an inconsistency in the internal field-name-to-index mapping within the time-series bucket catalog. Under certain conditions this can result in arbitrary code execution.This issue impacts MongoDB Server v5.0 versions prior to 5.0.33, v6.0 versions prior to 6.0.28, v7.0 versions prior to 7.0.34, v8.0 versions prior to 8.0.23, v8.2 versions prior to 8.2.9 and v8.3 versions prior to 8.3.2.</p>
 <br> CVSS Score has been rated as 8.7]]></description>
      <pubDate>Tue, 12 May 2026 23:59:43 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-126021</link>
      <guid>https://jira.mongodb.org/browse/SERVER-126021</guid>
    </item>
    <item>
      <title>Ops Manager RCE via webhook body (CVE-2026-8431)</title>
      <description><![CDATA[<p>An administrative user with access to configure webhooks can execute arbitrary commands by configuring and then triggering webhooks containing specific FreeMarker template syntax.This issue affects all MongoDB Ops Manager 7.0 versions and MongoDB Ops Manager versions 8.0.22 and prior.</p>
 <br> CVSS Score has been rated as 9.4]]></description>
      <pubDate>Tue, 12 May 2026 18:37:47 GMT</pubDate>
      <link>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-8.0.23</link>
      <guid>https://www.mongodb.com/docs/ops-manager/current/release-notes/application/#onprem-server-8.0.23</guid>
    </item>
    <item>
      <title>Integer Overflow in GridFS chunkSize Leading to Heap Allocation Failure (CVE-2025-14911)</title>
      <description><![CDATA[<p>User-controlled chunkSize metadata from MongoDB lacks appropriate validation allowing malformed GridFS metadata to overflow the bounding container.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 27 Jan 2026 17:29:21 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/CDRIVER-6125</link>
      <guid>https://jira.mongodb.org/browse/CDRIVER-6125</guid>
    </item>
    <item>
      <title>MongoDB Shell may be susceptible to control character injection via pasting (CVE-2025-1692)</title>
      <description><![CDATA[<p>The MongoDB Shell may be susceptible to control character injection where an attacker with control of the users clipboard could manipulate them to paste text into mongosh that evaluates arbitrary code. Control characters in the pasted text can be used to obfuscate malicious code. This issue affects mongosh versions prior to 2.3.9</p>
 <br> CVSS Score has been rated as 6.3]]></description>
      <pubDate>Thu, 27 Feb 2025 12:37:00 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOSH-2025</link>
      <guid>https://jira.mongodb.org/browse/MONGOSH-2025</guid>
    </item>
    <item>
      <title>MongoDB Shell may be susceptible to control character Injection via shell output (CVE-2025-1693)</title>
      <description><![CDATA[<p>The MongoDB Shell may be susceptible to control character injection where an attacker with control over the database cluster contents can inject control characters into the shell output. This may result in the display of falsified messages that appear to originate from mongosh or the underlying operating system, potentially misleading users into executing unsafe actions.The vulnerability is exploitable only when mongosh is connected to a cluster that is partially or fully controlled by an attacker.This issue affects mongosh versions prior to 2.3.9</p>
 <br> CVSS Score has been rated as 3.9]]></description>
      <pubDate>Thu, 27 Feb 2025 12:39:37 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOSH-2026</link>
      <guid>https://jira.mongodb.org/browse/MONGOSH-2026</guid>
    </item>
    <item>
      <title>MongoDB Compass may be susceptible to local privilege escalation in Windows (CVE-2025-1755)</title>
      <description><![CDATA[<p>MongoDB Compass may be susceptible to local privilege escalation under certain conditions potentially enabling unauthorized actions on a user&#39;s system with elevated privileges, when a crafted file is stored in C:\node_modules. This issue affects MongoDB Compass prior to 1.42.1</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Thu, 27 Feb 2025 15:24:07 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/COMPASS-9058</link>
      <guid>https://jira.mongodb.org/browse/COMPASS-9058</guid>
    </item>
    <item>
      <title>MongoDB Shell may be susceptible to local privilege escalation in Windows (CVE-2025-1756)</title>
      <description><![CDATA[<p>mongosh may be susceptible to local privilege escalation under certain conditions potentially enabling unauthorized actions on a user&#39;s system with elevated privilege, when a crafted file is stored in C:\node_modules. This issue affects mongosh prior to 2.3.0</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Thu, 27 Feb 2025 15:28:11 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/MONGOSH-2028</link>
      <guid>https://jira.mongodb.org/browse/MONGOSH-2028</guid>
    </item>
    <item>
      <title>MongoDB C Driver bson library may be susceptible to buffer overflow (CVE-2025-0755)</title>
      <description><![CDATA[<p>The various bson_appendfunctions in the MongoDB C driver library may be susceptible to buffer overflow when performing operations that could result in a final BSON document which exceeds the maximum allowable size (INT32_MAX), resulting in a segmentation fault and possible application crash. This issue affected libbson versions prior to 1.27.5, MongoDB Server v8.0 versions prior to 8.0.1 and MongoDB Server v7.0 versions prior to 7.0.16</p>
 <br> CVSS Score has been rated as 8.4]]></description>
      <pubDate>Tue, 18 Mar 2025 09:01:04 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-94461</link>
      <guid>https://jira.mongodb.org/browse/SERVER-94461</guid>
    </item>
    <item>
      <title>Malformed MongoDB wire protocol messages may cause mongos to crash (CVE-2025-3083)</title>
      <description><![CDATA[<p>Specifically crafted MongoDB wire protocol messages can cause mongos to crash during command validation. This can occur without using an authenticated connection. This issue affects MongoDB v5.0 versions prior to 5.0.31, MongoDB v6.0 versions prior to6.0.20 and MongoDB v7.0 versions prior to 7.0.16</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Tue, 01 Apr 2025 11:12:31 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103152</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103152</guid>
    </item>
    <item>
      <title>User may override a view&#39;s collation and gain unauthorized access to underlying data (CVE-2025-3082)</title>
      <description><![CDATA[<p>A user authorized to access a view may be able to alter the intended collation, allowing them to access to a different or unintended view of underlying data. This issue affects MongoDB Server v5.0 version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.20, MongoDB Server v7.0 version prior to 7.0.14 and MongoDB Server v7.3 versions prior to 7.3.4.</p>
 <br> CVSS Score has been rated as 3.1]]></description>
      <pubDate>Tue, 01 Apr 2025 11:08:06 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103151</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103151</guid>
    </item>
    <item>
      <title>MongoDB Server may crash due to improper validation of explain command (CVE-2025-3084)</title>
      <description><![CDATA[<p>When run on commands with certain arguments set, explain may fail to validate these arguments before using them. This can lead to crashes in router servers. This affects MongoDB Server v5.0 prior to 5.0.31, MongoDB Server v6.0 prior to 6.0.20, MongoDB Server v7.0 prior to 7.0.16 and MongoDB Server v8.0 prior to 8.0.4</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Tue, 01 Apr 2025 11:14:19 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103153</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103153</guid>
    </item>
    <item>
      <title>MongoDB Server running on Linux may allow unexpected connections where intermediate certificates are revoked (CVE-2025-3085)</title>
      <description><![CDATA[<p>A MongoDB server under specific conditions running on Linux with TLS and CRL revocation status checking enabled, fails to check the revocation status of the intermediate certificates in the peer&#39;s certificate chain. In cases of MONGODB-X509, which is not enabled by default, this may lead to improper authentication. This issue may also affect intra-cluster authentication. This issue affects MongoDB Server v5.0 versions prior to 5.0.31, MongoDB Server v6.0 versions prior to 6.0.20, MongoDB Server v7.0 versions prior to 7.0.16 and MongoDB Server v8.0 versions prior to 8.0.4.Required Configuration :MongoDB Server must be running on Linux Operating Systems and CRL revocation status checking must be enabled</p>
 <br> CVSS Score has been rated as 8.1]]></description>
      <pubDate>Tue, 01 Apr 2025 12:05:05 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-95445</link>
      <guid>https://jira.mongodb.org/browse/SERVER-95445</guid>
    </item>
    <item>
      <title>Running certain aggregation operations with the SBE engine may lead to unexpected behavior on MongoDB Server (CVE-2025-6706)</title>
      <description><![CDATA[<p>An authenticated user may trigger a use after free that may result in MongoDB Server crash and other unexpected behavior, even if the user does not have authorization to shut down a server.The crash is triggered on affected versions by issuing an aggregation framework operation using a specific combination of rarely-used aggregation pipeline expressions. This issue affects MongoDB Server v6.0 version prior to 6.0.21, MongoDB Server v7.0 version prior to 7.0.17 and MongoDB Server v8.0 version prior to 8.0.4 when the SBE engine is enabled.</p>
 <br> CVSS Score has been rated as 5]]></description>
      <pubDate>Thu, 26 Jun 2025 14:00:22 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106746</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106746</guid>
    </item>
    <item>
      <title>Race condition in privilege cache invalidation cycle (CVE-2025-6707)</title>
      <description><![CDATA[<p>Under certain conditions, an authenticated user request may execute with stale privileges following an intentional change by an authorized administrator. This issue affects MongoDB Server v5.0 version prior to 5.0.31, MongoDB Server v6.0 version prior to 6.0.24, MongoDB Server v7.0 version prior to 7.0.21 and MongoDB Server v8.0 version prior to 8.0.5.</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Thu, 26 Jun 2025 14:04:46 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-93497</link>
      <guid>https://jira.mongodb.org/browse/SERVER-93497</guid>
    </item>
    <item>
      <title>Pre-Authentication Denial of Service Vulnerability in MongoDB Server&#39;s OIDC Authentication (CVE-2025-6709)</title>
      <description><![CDATA[<p>The MongoDB Server is susceptible to a denial of service vulnerability due to improper handling of specific date values in JSON input when using OIDC authentication. This can be reproduced using the mongo shell to send a malicious JSON payload leading to an invariant failure and server crash. This issue affects MongoDB Server v7.0 versions prior to 7.0.17 and MongoDB Server v8.0 versions prior to 8.0.5.The same issue affects MongoDB Server v6.0 versions prior to 6.0.21, but an attacker can only induce denial of service after authenticating.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Thu, 26 Jun 2025 14:07:04 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106748</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106748</guid>
    </item>
    <item>
      <title>Pre-authentication Denial of Service Stack Overflow Vulnerability in JSON Parsing via Excessive Recursion in MongoDB (CVE-2025-6710)</title>
      <description><![CDATA[<p>MongoDB Server may be susceptible to stack overflow due to JSON parsing mechanism, where specifically crafted JSON inputs may induce unwarranted levels of recursion, resulting in excessive stack space consumption. Such inputs can lead to a stack overflow that causes the server to crash which could occur pre-authorisation. This issue affects MongoDB Server v7.0 versions prior to 7.0.17 and MongoDB Server v8.0 versions prior to 8.0.5.The same issue affects MongoDB Server v6.0 versions prior to 6.0.21, but an attacker can only induce denial of service after authenticating.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Thu, 26 Jun 2025 14:09:29 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106749</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106749</guid>
    </item>
    <item>
      <title>Certain Queries with Duplicate _id Fields May Cause MongoDB Server to Crash (CVE-2025-7259)</title>
      <description><![CDATA[<p>An authorized user can issue queries with duplicate _id fields, that leads to unexpected behavior in MongoDB Server, which may result to crash. This issue can only be triggered by authorized users and cause Denial of Service. This issue affects MongoDB Server v8.1 version 8.1.0.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Mon, 07 Jul 2025 15:59:01 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-102693</link>
      <guid>https://jira.mongodb.org/browse/SERVER-102693</guid>
    </item>
    <item>
      <title>Incomplete Redaction of Sensitive Information in MongoDB Server Logs (CVE-2025-6711)</title>
      <description><![CDATA[<p>An issue has been identified in MongoDB Server where unredacted queries may inadvertently appear in server logs when certain error conditions are encountered. This issue affects MongoDB Server v8.0 versions prior to 8.0.5, MongoDB Server v7.0 versions prior to 7.0.18 and MongoDB Server v6.0 versions prior to 6.0.21.</p>
 <br> CVSS Score has been rated as 4.4]]></description>
      <pubDate>Mon, 07 Jul 2025 14:42:16 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-98720</link>
      <guid>https://jira.mongodb.org/browse/SERVER-98720</guid>
    </item>
    <item>
      <title>MongoDB Server may allow queries to be terminated by unauthorized users (CVE-2025-13643)</title>
      <description><![CDATA[<p>A user with access to the cluster with a limited set of privilege actions may be able to terminate queries that are being executed by other users. This may cause a denial of service by preventing a fraction of queries from successfully completing. This issue affects MongoDB Server v7.0 versions prior to 7.0.26 and MongoDB Server v8.0 versions prior to 8.0.14</p>
 <br> CVSS Score has been rated as 3.1]]></description>
      <pubDate>Tue, 25 Nov 2025 05:16:24 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-103582</link>
      <guid>https://jira.mongodb.org/browse/SERVER-103582</guid>
    </item>
    <item>
      <title>MongoDB Server may be susceptible to privilege escalation due to $mergeCursors stage (CVE-2025-6713)</title>
      <description><![CDATA[<p>An unauthorized user may leverage a specially crafted aggregation pipeline to access data without proper authorization due to improper handling of the $mergeCursors stage in MongoDB Server. This may lead to access to data without further authorisation. This issue affects MongoDB Server MongoDB Server v8.0 versions prior to 8.0.7, MongoDB Server v7.0 versions prior to 7.0.20 and MongoDB Server v6.0 versions prior to 6.0.22</p>
 <br> CVSS Score has been rated as 7.7]]></description>
      <pubDate>Mon, 07 Jul 2025 14:46:36 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106752</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106752</guid>
    </item>
    <item>
      <title>Incorrect Handling of incomplete data may prevent mongoS from Accepting New Connections (CVE-2025-6714)</title>
      <description><![CDATA[<p>MongoDB Server&#39;s mongos component can become unresponsive to new connections due to incorrect handling of incomplete data. This affects MongoDB when configured with load balancer support. This issue affects MongoDB Server v6.0 prior to 6.0.23, MongoDB Server v7.0 prior to 7.0.20 and MongoDB Server v8.0 prior to 8.0.9Required Configuration:This affects MongoDB sharded clusters when configured with load balancer support for mongos using HAProxy on specified ports.</p>
 <br> CVSS Score has been rated as 7.5]]></description>
      <pubDate>Mon, 07 Jul 2025 14:48:48 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-106753</link>
      <guid>https://jira.mongodb.org/browse/SERVER-106753</guid>
    </item>
    <item>
      <title>MongoDB Server router will crash when incorrect lsid is set on a sharded query (CVE-2025-10059)</title>
      <description><![CDATA[<p>An improper setting of the lsid field on any sharded query can cause a crash in MongoDB routers. This issue occurs when a generic argument (lsid) is provided in a case when it is not applicable. This affects MongoDB Server v6.0 versions prior to 6.0.x, MongoDB Server v7.0 versions prior to 7.0.18 and MongoDB Server v8.0 versions prior to 8.0.6.</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 05 Sep 2025 20:26:52 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-100901</link>
      <guid>https://jira.mongodb.org/browse/SERVER-100901</guid>
    </item>
    <item>
      <title>MongoDB may be susceptible to Invariant Failure in Transactions due Upsert Operation (CVE-2025-10060)</title>
      <description><![CDATA[<p>MongoDB Server may allow upsert operations retried within a transaction to violate unique index constraints, potentially causing an invariant failure and server crash during commit. This issue may be triggered by improper WriteUnitOfWork state management.  This issue affects MongoDB Server v6.0 versions prior to 6.0.25, MongoDB Server v7.0 versions prior to 7.0.22 and MongoDB Server v8.0 versions prior to 8.0.12</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 05 Sep 2025 20:39:14 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-95524</link>
      <guid>https://jira.mongodb.org/browse/SERVER-95524</guid>
    </item>
    <item>
      <title>Malformed $group Query May Cause MongoDB Server to Crash (CVE-2025-10061)</title>
      <description><![CDATA[<p>An authorized user can cause a crash in the MongoDB Server through a specially crafted $group query. This vulnerability is related to the incorrect handling of certain accumulator functions when additional parameters are specified within the $group operation. This vulnerability could lead to denial of service if triggered repeatedly. This issue affects MongoDB Server v6.0 versions prior to 6.0.25, MongoDB Server v7.0 versions prior to 7.0.22, MongoDB Server v8.0 versions prior to 8.0.12 and MongoDB Server v8.1 versions prior to 8.1.2</p>
 <br> CVSS Score has been rated as 6.5]]></description>
      <pubDate>Fri, 05 Sep 2025 20:48:25 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-99616</link>
      <guid>https://jira.mongodb.org/browse/SERVER-99616</guid>
    </item>
    <item>
      <title>MongoDB Windows installation MSI may leave ACLs unset on custom installation directories (CVE-2025-10491)</title>
      <description><![CDATA[<p>The MongoDB Windows installation MSI may leave ACLs unset on custom installation directories allowing a local attacker to introduce executable code to MongoDB&#39;s process via DLL hijacking. This issue affects MongoDB Server v6.0 version prior to 6.0.25, MongoDB Server v7.0 version prior to 7.0.21 and MongoDB Server v8.0 version prior to 8.0.5</p>
 <br> CVSS Score has been rated as 7.8]]></description>
      <pubDate>Mon, 15 Sep 2025 16:04:54 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-51366</link>
      <guid>https://jira.mongodb.org/browse/SERVER-51366</guid>
    </item>
    <item>
      <title>MongoDB Connector for BI installation MSI leave ACLs unset on custom installation directories (CVE-2025-11535)</title>
      <description><![CDATA[<p>MongoDB Connector for BI installation viaMSIon 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.</p>
 <br> CVSS Score has been rated as ]]></description>
      <pubDate>Wed, 08 Oct 2025 22:07:18 GMT</pubDate>
      <link>https://www.mongodb.com/docs/bi-connector/current/release-notes/#bi-2.14.25</link>
      <guid>https://www.mongodb.com/docs/bi-connector/current/release-notes/#bi-2.14.25</guid>
    </item>
    <item>
      <title>Configuration may unexpectedly disable certificate validation (CVE-2025-11695)</title>
      <description><![CDATA[<p>When tlsInsecure=False appears in a connection string, certificate validation is disabled.This vulnerability affects MongoDB Rust Driver versions prior to v3.2.5</p>
 <br> CVSS Score has been rated as 8]]></description>
      <pubDate>Mon, 13 Oct 2025 16:22:57 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/RUST-2264</link>
      <guid>https://jira.mongodb.org/browse/RUST-2264</guid>
    </item>
    <item>
      <title>Use-after-free in the MongoDB server query planner may lead to crash or undefined behavior (CVE-2025-11979)</title>
      <description><![CDATA[<p>An authorized user may crash the MongoDB server by causing buffer over-read. This can be done by issuing a DDL operation while queries are being issued, under some conditions. This issue affects MongoDB Server v7.0 versions prior to 7.0.25, MongoDB Server v8.0 versions prior to 8.0.15, and MongoDB Server version 8.2.0.</p>
 <br> CVSS Score has been rated as 5.3]]></description>
      <pubDate>Mon, 20 Oct 2025 17:47:57 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-105873</link>
      <guid>https://jira.mongodb.org/browse/SERVER-105873</guid>
    </item>
    <item>
      <title>MongoDB Atlas SQL ODBC driver installation via MSI may leave ACLs unset on custom installation directories (CVE-2025-11575)</title>
      <description><![CDATA[<p>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.</p>
 <br> CVSS Score has been rated as ]]></description>
      <pubDate>Thu, 23 Oct 2025 00:22:00 GMT</pubDate>
      <link>https://www.mongodb.com/docs/atlas/release-notes/sql/</link>
      <guid>https://www.mongodb.com/docs/atlas/release-notes/sql/</guid>
    </item>
    <item>
      <title>MongoDB BI Connector ODBC driver installation via MSI may leave ACLs unset on custom installation directories (CVE-2025-12100)</title>
      <description><![CDATA[<p>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.</p>
 <br> CVSS Score has been rated as ]]></description>
      <pubDate>Thu, 23 Oct 2025 21:02:18 GMT</pubDate>
      <link>https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.7</link>
      <guid>https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.7</guid>
    </item>
    <item>
      <title>Malformed KMIP response may result in access violation (CVE-2025-12657)</title>
      <description><![CDATA[<p>The KMIP response parser built into mongo binaries is overly tolerant of certain malformed packets, and may parse them into invalid objects. Later reads of this object can result in read access violations.</p>
 <br> CVSS Score has been rated as ]]></description>
      <pubDate>Mon, 03 Nov 2025 21:03:25 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-101230</link>
      <guid>https://jira.mongodb.org/browse/SERVER-101230</guid>
    </item>
    <item>
      <title>Bulk write with options may read invalid memory (CVE-2025-12119)</title>
      <description><![CDATA[<p>A mongoc_bulk_operation_t may read invalid memory if large options are passed.</p>
 <br> CVSS Score has been rated as ]]></description>
      <pubDate>Tue, 18 Nov 2025 20:21:08 GMT</pubDate>
      <link>https://github.com/mongodb/mongo-php-driver/releases/tag/1.21.2</link>
      <guid>https://github.com/mongodb/mongo-php-driver/releases/tag/1.21.2</guid>
    </item>
    <item>
      <title>Time-series operations may cause internal BSON size limit to be exceed (CVE-2025-13507)</title>
      <description><![CDATA[<p>Inconsistent object size validation in time series processing logic may result in later processing of oversized BSON documents leading to an assert failing and process termination. This issue impacts MongoDB Server v7.0 versions prior to 7.0.26, v8.0 versions prior to 8.0.16 and MongoDB server v8.2 versions prior to 8.2.1.</p>
 <br> CVSS Score has been rated as 7.1]]></description>
      <pubDate>Tue, 25 Nov 2025 04:52:47 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-108565</link>
      <guid>https://jira.mongodb.org/browse/SERVER-108565</guid>
    </item>
    <item>
      <title>Improper Certificate Validation May Allow Successful TLS Handshaking Despite Invalid Extended Key Usage Fields in MongoDB Server (CVE-2025-12893)</title>
      <description><![CDATA[<p>Clients may successfully perform a TLS handshake with a MongoDB server despite presenting a client certificate not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = clientAuth may still be successfully authenticated via the TLS handshake as a client. This issue is specific to MongoDB servers running on Windows or Apple as the expected validation behavior functions correctly on Linux systems.Additionally, MongoDB servers may successfully establish egress TLS connections with servers that present server certificates not aligning with the documented Extended Key Usage (EKU) requirements. A certificate that specifies extendedKeyUsage but is missing extendedKeyUsage = serverAuth may still be successfully authenticated via the TLS handshake as a server. This issue is specific to MongoDB servers running on Apple as the expected validation behavior functions correctly on both Linux and Windows systems. This vulnerability affects MongoDB Server v7.0 versions prior to 7.0.26, MongoDB Server v8.0 versions prior to 8.0.16 and MongoDB Server v8.2 versions prior to 8.2.2</p>
 <br> CVSS Score has been rated as 4.2]]></description>
      <pubDate>Tue, 25 Nov 2025 05:07:17 GMT</pubDate>
      <link>https://jira.mongodb.org/browse/SERVER-105783</link>
      <guid>https://jira.mongodb.org/browse/SERVER-105783</guid>
    </item><atom:link href="https://www.mongodb.com/resources/products/alerts/rss" rel="self" type="application/rss+xml" /></channel></rss>