Bitnami package
mongodb
pkg:bitnami/mongodb
Vulnerabilities (161)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2026-5170 | Med | 5.3 | >= 7.0.0, < 7.0.31 | 7.0.31 | Mar 30, 2026 | A user with access to the cluster with a limited set of privilege actions can trigger a crash of a mongod 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 d | |
| CVE-2026-4358 | Med | 6.4 | >= 7.0.0, < 7.0.31 | 7.0.31 | Mar 17, 2026 | 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. | |
| CVE-2026-4148 | Hig | 8.8 | >= 7.0.0, < 7.0.31 | 7.0.31 | Mar 17, 2026 | 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. | |
| CVE-2026-4147 | Med | 6.5 | >= 7.0.0, < 7.0.31 | 7.0.31 | Mar 17, 2026 | An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command. | |
| CVE-2026-25613 | Med | 6.5 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | An authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index. | |
| CVE-2026-25610 | Med | 6.5 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | An authorized user may trigger a server crash by running a $geoNear pipeline with certain invalid index hints. | |
| CVE-2026-25609 | Med | 5.4 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | Incorrect validation of the profile command may result in the determination that a request altering the 'filter' is read-only. | |
| CVE-2026-1850 | Med | 6.5 | >= 8.0.0, < 8.0.18 | 8.0.18 | Feb 10, 2026 | Complex queries can cause excessive memory usage in MongoDB Query Planner resulting in an Out-Of-Memory Crash. | |
| CVE-2026-1849 | Med | 6.5 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | 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. | |
| CVE-2026-1848 | Hig | 7.5 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | 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. | |
| CVE-2026-1847 | Med | 6.5 | >= 7.0.0, < 7.0.29 | 7.0.29 | Feb 10, 2026 | 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. | |
| CVE-2025-14847 | Hig | 7.5 | KEV | >= 4.4.0, < 4.4.30 | 4.4.30 | Dec 19, 2025 | 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 |
| CVE-2025-14345 | Med | 4.2 | >= 7.0.0, < 7.0.26 | 7.0.26 | Dec 9, 2025 | A post-authentication flaw 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 | |
| CVE-2025-13644 | Med | 6.5 | >= 7.0.0, < 7.0.26 | 7.0.26 | Nov 25, 2025 | 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 affect | |
| CVE-2025-13643 | Low | 3.1 | >= 7.0.0, < 7.0.26 | 7.0.26 | Nov 25, 2025 | 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 Serve | |
| CVE-2025-13507 | Med | 6.5 | >= 7.0.0, < 7.0.26 | 7.0.26 | Nov 25, 2025 | 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 | |
| CVE-2025-12893 | Med | 4.2 | >= 7.0.0, < 7.0.26 | 7.0.26 | Nov 25, 2025 | 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 st | |
| CVE-2025-12657 | Med | 5.0 | >= 6.0.0, < 7.0.22 | 7.0.22 | Nov 3, 2025 | 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. | |
| CVE-2025-11979 | Med | 5.3 | >= 7.0.0, < 7.0.25 | 7.0.25 | Oct 20, 2025 | 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 | |
| CVE-2025-10061 | Med | 6.5 | >= 6.0.0, < 6.0.25 | 6.0.25 | Sep 5, 2025 | 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 c |
- affected >= 7.0.0, < 7.0.31fixed 7.0.31
A user with access to the cluster with a limited set of privilege actions can trigger a crash of a mongod 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 d
- affected >= 7.0.0, < 7.0.31fixed 7.0.31
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.
- affected >= 7.0.0, < 7.0.31fixed 7.0.31
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.
- affected >= 7.0.0, < 7.0.31fixed 7.0.31
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
An authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
An authorized user may trigger a server crash by running a $geoNear pipeline with certain invalid index hints.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
Incorrect validation of the profile command may result in the determination that a request altering the 'filter' is read-only.
- affected >= 8.0.0, < 8.0.18fixed 8.0.18
Complex queries can cause excessive memory usage in MongoDB Query Planner resulting in an Out-Of-Memory Crash.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
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.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
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.
- affected >= 7.0.0, < 7.0.29fixed 7.0.29
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.
- affected >= 4.4.0, < 4.4.30fixed 4.4.30
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
- affected >= 7.0.0, < 7.0.26fixed 7.0.26
A post-authentication flaw 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
- affected >= 7.0.0, < 7.0.26fixed 7.0.26
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 affect
- affected >= 7.0.0, < 7.0.26fixed 7.0.26
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 Serve
- affected >= 7.0.0, < 7.0.26fixed 7.0.26
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
- affected >= 7.0.0, < 7.0.26fixed 7.0.26
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 st
- affected >= 6.0.0, < 7.0.22fixed 7.0.22
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.
- affected >= 7.0.0, < 7.0.25fixed 7.0.25
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
- affected >= 6.0.0, < 6.0.25fixed 6.0.25
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 c
Page 6 of 9