Vulnerability from bitnami_vulndb
Published
2026-02-26 08:47
Modified
2026-02-26 09:13
Summary
MongoDB Server may crash when inserting large documents
Details
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": [
{
"package": {
"ecosystem": "Bitnami",
"name": "mongodb",
"purl": "pkg:bitnami/mongodb"
},
"ranges": [
{
"events": [
{
"introduced": "7.0.0"
},
{
"fixed": "7.0.29"
},
{
"introduced": "8.0.0"
},
{
"fixed": "8.0.18"
},
{
"introduced": "8.2.0"
},
{
"fixed": "8.2.4"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
],
"aliases": [
"CVE-2026-1847"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:mongodb:mongodb:*:*:*:*:-:*:*:*"
],
"severity": "High"
},
"details": "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.",
"id": "BIT-mongodb-2026-1847",
"modified": "2026-02-26T09:13:58.886Z",
"published": "2026-02-26T08:47:38.190Z",
"references": [
{
"type": "WEB",
"url": "https://jira.mongodb.org/browse/SERVER-113532"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-1847"
}
],
"schema_version": "1.6.2",
"summary": "MongoDB Server may crash when inserting large documents"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…