CVE-2026-25613: An unsafe cast in the MongoDB query planner can result in a segmentation fault.
An authorized user may disable the MongoDB server by issuing a query against a collection that contains an invalid compound wildcard index.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-25613?
CVE-2026-25613 has been rated as a high-severity vulnerability due to its potential to cause a segmentation fault in the MongoDB server.
How do I fix CVE-2026-25613?
To fix CVE-2026-25613, ensure you apply the latest patches provided by MongoDB that address unsafe casts in the query planner.
Who is affected by CVE-2026-25613?
Authorized users running MongoDB with invalid compound wildcard indexes may be affected by CVE-2026-25613.
What are the potential impacts of CVE-2026-25613?
The potential impact of CVE-2026-25613 includes server crashes and denial of service due to segmentation faults when affected queries are executed.
What is the cause of the vulnerability in CVE-2026-25613?
CVE-2026-25613 is caused by an unsafe cast in the MongoDB query planner that occurs when processing certain invalid queries.