12/26/2025
at
9:46:09 PM
No, but it's pretty common IME to create an Atlas cluster that has internet-wide access (0.0.0.0/0) when testing and forgetting to turn this off. According to https://jira.mongodb.org/browse/SERVER-115508, this affects unauthenticated ops. Based on the repro code itself, it looks like this happens way before authentication is checked for the corresponding OP at the OP_MSG decoding level.So if you're using Atlas, check that your Cluster has auto upgraded already. If you're using 0.0.0.0/0, stop doing that and prefer a limited IP address range and even better, use VPC Peering or other security/network boundary features.
by erdaniels
12/26/2025
at
10:06:11 PM
We received communication that all Atlas clusters were upgraded with the fix before the vulnerability was announced.
by computerfan494
12/27/2025
at
12:19:00 AM
This is a good example of a benefit of certificate-based authentication option for MongoDB, because you need to at least present a valid client certificate to transmit any data.
by yearolinuxdsktp
12/29/2025
at
5:29:34 PM
> No, but it's pretty common IME to create an Atlas cluster that has internet-wide access (0.0.0.0/0) when testing and forgetting to turn this off.That is a ridiculous default.
by nailer