MongoDB Server CVE-2026-120822 and CVE-2026-120825 Authorization Vulnerabilities
Is it fixed? Not yet.
Ongoing since Nov 10, 21:19 UTC. First reported Nov 10, 21:19 UTC. Not on the vendor’s status page yet.
What happened
MongoDB Server suffers from multiple high-severity authorization vulnerabilities involving replication-related administrative commands and the aggregation framework's view validation. Users with limited privileges can exploit these flaws to read and relocate unauthorized collections or access restricted database views.
What caused it?
Authorization checks for replication administrative commands relied on client-supplied values, and privilege evaluations during view definition validation failed to cover nested pipeline portions.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
MongoDB Server: CVE-2026-120822 (High)
Source
Evidence
2 reports · 2 CVEShow
- [1]CVE First reportMongoDB Server: CVE-2026-120822 (High)(opens security advisory in a new tab)
High severity. MongoDB Server may omit an authorization check on the resource that a replication-related administrative command actually targets, because that check is conditioned on a value taken from the client's own request. A user holding backup and restore privileges may therefore read and relocate collections outside the set that user is permitted to access. This may result in unintended access to data and unintended changes to the collection catalog.
by Tenable 0upvotes 0comments
- [2]CVEaggregation framework of MongoDB Server: CVE-2026-120825 (High)(opens security advisory in a new tab)
High severity. An authorization weakness in the aggregation framework of MongoDB Server may allow an authenticated user holding only basic database privileges to read the contents of collections in a database for which they have not been granted read access. The privilege evaluation performed while a view definition is validated does not cover a nested portion of the supplied pipeline, so the resulting view returns data the user is otherwise refused. This may result in unintended access to…
by Tenable 0upvotes 0comments95% match
FAQ
What happened in the MongoDB issue?
MongoDB Server suffers from multiple high-severity authorization vulnerabilities involving replication-related administrative commands and the aggregation framework's view validation. Users with limited privileges can exploit these flaws to read and relocate unauthorized collections or access restricted database views.
What is affected by the MongoDB issue?
MongoDB.
When did the MongoDB issue start and end?
It started Nov 10, 21:19 UTC and is still ongoing (8 d 7 h so far). This page updates as it develops.
How do I get alerts for MongoDB?
Subscribe to the MongoDB RSS feed for every new MongoDB incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether MongoDB is down. MongoDB feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 2 reports from 1 independent source.