Calling createIndex with certain index types can crash mongod

Post-authentication CPU utilization DoS via $trim/$ltrim/$rtrim operators

Post-authentication use-after-free error in $_internalJsEmit and mapreduce commands

Post-auth memory exhaustion via bitwise match expressions

Post-auth null pointer dereference when aggregating against a view with empty search pipeline

An unsafe cast in the MongoDB query planner can result in a segmentation fault.

Invalid $geoNear index hint may cause server crash

Internal ResourceId collision may affect unrelated collections

MongoDB Server may allow queries to be terminated by unauthorized users

Time-series operations may cause internal BSON size limit to be exceed

Malformed $group Query May Cause MongoDB Server to Crash

MongoDB Server router will crash when incorrect lsid is set on a sharded query

Malformed KMIP response may result in access violation

Cross-Shard Failovers May Lead to Partial Transaction Commit in MongoDB Server

Improper Certificate Validation May Allow Successful TLS Handshaking Despite Invalid Extended Key Usage Fields in MongoDB Server

Schema validation log messages may not redact user data

Stack memory disclosure in filemd5 command

profile command may permit unauthorized configuration