MongoDB Data Breach History
WebsiteMongoDB is a document-oriented NoSQL database platform.
This page shows all data breaches of MongoDB. View the complete breach timeline, records exposed, root causes, and AI breach risk score. BreachHistory tracks disclosed data breaches worldwide.
Data Breach Timeline — All MongoDB Breaches
- 2023 2023 MongoDB — phishing/social engineering against corporate systems; customer account metadata exposure Unknown records Share
- 2019 2019 — Databases Unknown records Share
- 2019 2019 MongoDB — 275M records, unsecured databases 275.0M records Share
- 2019 2019 — MongoDB: Poor security / misconfiguration, 202,000,000 records 202.0M records Share
- 2017 2017 — MongoDB: Three hacking groups are once again targeting… 26.0K records Share
MongoDB Data Breach Summary
This page tracks the MongoDB data breach history and cybersecurity incidents affecting MongoDB (United States). BreachHistory currently indexes 5 publicly disclosed or catalogued incidents spanning 2017 through 2023, with approximately 477.0 million records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.
The MongoDB breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed.
Largest MongoDB Data Breaches
The largest indexed incidents include the 2019 MongoDB — 275M records, unsecured databases, the 2019 — MongoDB: Poor security / misconfiguration, 202,000,000 records, and the 2017 — MongoDB: Three hacking groups are once again targeting…. Record counts originating from threat actors or leak sites should be treated as estimates unless confirmed by MongoDB or a regulator. Below is the list of large data breaches:
- 2019 2019 MongoDB — 275M records, unsecured databases — about 275.0M records exposed · Catalogued incident
- 2019 2019 — MongoDB: Poor security / misconfiguration, 202,000,000 records — about 202.0M records exposed · Catalogued incident
- 2017 2017 — MongoDB: Three hacking groups are once again targeting… — about 26.0K records exposed · Catalogued incident
What Information Was Exposed?
Depending on the incident, exposed data may include email addresses, phone numbers, names, physical addresses, health and medical (PHI) records, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.
MongoDB Data Breach 2026
At the time of this update, no MongoDB data breach has been catalogued for 2026. New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.
What To Do If You Were Affected
If you believe your account may have been involved in a MongoDB data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.
This MongoDB breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.