|
Vulnerability Type |
Use-after-free in MongoDB Server replica set replication (CVE-2026-118383), plus 18 further MongoDB Server vulnerabilities fixed in the same release. |
|
Severity factors |
MongoDB rates CVE-2026-118383 critical (CVSS 9.5). It can be triggered without authentication by anyone who can reach MongoDB's port on a replica set member, and may crash the server or allow remote code execution. FileCloud's default installation runs a single MongoDB instance that accepts connections only from the server itself, so the vulnerability does not apply to it. MongoDB found the issue internally and is not aware of any exploitation. |
|
Versions affected |
All FileCloud Server versions up to and including 23.263.3, on Windows and Linux. Only deployments that run MongoDB as a replica set, the high availability setup, are exposed to CVE-2026-118383. |
|
Version fixed |
To be released (FileCloud 23.264, due December 2026, bundling MongoDB 8.0.38). |
Description
On 10 November 2026, MongoDB released MongoDB Server 8.0.37, which fixes 19 vulnerabilities in the 8.0 line, and 8.0.38, which adds one build fix. The most serious, CVE-2026-118383, is a use-after-free that a newly elected replica set primary can hit while it catches up with the other members. It can be triggered without authentication and may crash the server or allow remote code execution. The same vulnerability affects MongoDB 7.0 before 7.0.48.
FileCloud bundles MongoDB Server: 23.263.0 to 23.263.2 bundle MongoDB 8.0.29, and 23.263.3 bundles 8.0.32. Both are in the affected range, so vulnerability scanners will report every current FileCloud release.
Whether a FileCloud server is exposed depends on how it runs MongoDB:
-
Default installation (single server): MongoDB runs as a single instance that accepts connections only from 127.0.0.1. CVE-2026-118383 needs a replica set, so it does not apply.
-
High availability (MongoDB replica set): affected. Anyone who can reach port 27017 on a replica set member can trigger CVE-2026-118383.
-
The other 18 vulnerabilities: none of them lets someone without a MongoDB login into a FileCloud installation. Most need MongoDB features that FileCloud does not use, such as time-series collections, queryable encryption, client-side field level encryption, sharding, change streams or server-side JavaScript, or a build that FileCloud does not ship, such as MongoDB Enterprise or macOS.
The fixes matter most where MongoDB can be reached from other machines. That is always the case in high availability deployments, and in any single-server installation where MongoDB has been configured to accept remote connections.
Interim mitigation
Until you can upgrade, make sure that only trusted hosts can reach MongoDB's port, 27017 by default. For a replica set member, the trusted hosts are the other replica set members, the FileCloud web/app nodes, and any server that backs up MongoDB. Apply the steps on every server that runs MongoDB.
Windows
-
Open a command prompt in
C:\xampp\mongodb\bin, then check the MongoDB version and whether this server is a replica set member:mongod.exe --version mongosh.exe --quiet --eval "db.hello().setName"A replica set member prints the name of its replica set; a single server prints nothing. If MongoDB does not accept connections on 127.0.0.1, add
--host <this server's IP address>to the second command. MongoDB 8.0 versions before 8.0.37, and 7.0 versions before 7.0.48, are affected. -
Check which address MongoDB listens on:
netstat -an | findstr :27017If the only address shown is
127.0.0.1:27017, MongoDB accepts connections from this server only and no further steps are needed. Any other address, such as0.0.0.0:27017or the server's IP address, means that it accepts remote connections: continue with step 3. -
In PowerShell, run as administrator, list the inbound firewall rules that allow MongoDB:
Get-NetFirewallPortFilter | Where-Object LocalPort -eq 27017 | Get-NetFirewallRule | Where-Object { $_.Enabled -eq 'True' -and $_.Direction -eq 'Inbound' -and $_.Action -eq 'Allow' } | Select-Object DisplayName Get-NetFirewallApplicationFilter | Where-Object Program -like '*mongod.exe' | Get-NetFirewallRule | Where-Object { $_.Enabled -eq 'True' -and $_.Direction -eq 'Inbound' -and $_.Action -eq 'Allow' } | Select-Object DisplayName -
Limit each listed rule to the trusted hosts. If no rule is listed on a replica set member, add one for the trusted hosts instead:
# Limit an existing rule Set-NetFirewallRule -DisplayName "<rule name>" -RemoteAddress <ip-address-1>,<ip-address-2>,<ip-address-3> # Or add a rule New-NetFirewallRule -DisplayName "MongoDB trusted hosts" -Direction Inbound -Protocol TCP -LocalPort 27017 -RemoteAddress <ip-address-1>,<ip-address-2>,<ip-address-3> -Action Allow
-
From a FileCloud web/app node, confirm that MongoDB can still be reached, and from a host that is not on the list, confirm that it cannot.
TcpTestSucceededshould beTrueandFalserespectively:Test-NetConnection <mongodb-server> -Port 27017
Note: These rules take effect only while Windows Firewall is on for the network profile in use. It then blocks inbound connections that no rule allows.
Linux
Run these commands as root.
-
Check the MongoDB version and whether this server is a replica set member:
mongod --version mongosh --quiet --eval "db.hello().setName"A replica set member prints the name of its replica set; a single server prints nothing. If MongoDB does not accept connections on 127.0.0.1, add
--host <this server's IP address>to the second command. -
Check which address MongoDB listens on:
ss -ltn | grep 27017If the only address shown is
127.0.0.1:27017, MongoDB accepts connections from this server only and no further steps are needed. Any other address means that it accepts remote connections: continue with step 3. -
Allow the trusted hosts and block everyone else. Run the allow command once for each trusted host:
# Ubuntu (ufw): add every allow rule before the deny rule ufw status ufw allow from <ip-address> to any port 27017 proto tcp ufw deny 27017/tcp # RHEL (firewalld) firewall-cmd --list-all firewall-cmd --permanent --remove-port=27017/tcp firewall-cmd --permanent --remove-service=mongodb firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<ip-address>" port port="27017" protocol="tcp" accept' firewall-cmd --reloadThe remove commands print a warning if the port or service was not open; this is expected. To add a host later on Ubuntu, use
ufw insert 1 allow from <ip-address> to any port 27017 proto tcpso that it comes before the deny rule.
-
From a FileCloud web/app node, confirm that MongoDB can still be reached, and from a host that is not on the list, confirm that it cannot:
timeout 5 bash -c '</dev/tcp/<mongodb-server>/27017' && echo open || echo closed
Note: If ufw status shows that ufw is inactive, or firewalld is not running, do not turn it on only for this change: its default rules can block SSH and FileCloud itself. Apply the restriction in your network firewall instead, or in your cloud provider's security group for port 27017.
Deployment notes for interim mitigation
Single-server installations: No action is required while MongoDB listens on 127.0.0.1 only, which is the default. If MongoDB was set up to accept remote connections and does not need them, set it back to listen on 127.0.0.1 in MongoDB's configuration file (bindIp), then restart MongoDB.
Multitenant deployments: All tenants share the same MongoDB, so the steps only need to be applied once on each MongoDB server.
High availability deployments: Apply the steps on every replica set member, including any arbiter. To avoid an outage, change one member at a time, and confirm that the FileCloud web/app nodes and the other members can still connect before moving on.
FileCloud Online: No action is required. FileCloud Online is not affected by these vulnerabilities.
Fix
-
FileCloud Server up to and including 23.263.3: We recommend upgrading to 23.264 when it is released (due December 2026). It bundles MongoDB 8.0.38. In a high availability deployment, upgrade one replica set member at a time, secondaries first, so that the cluster stays available.
-
MongoDB servers that you installed and manage yourself: Upgrade them now to MongoDB 8.0.37 or later on the 8.0 line, or 7.0.48 or later on the 7.0 line. You do not need to wait for FileCloud 23.264.
-
FileCloud Online: No action is required.
If you have any questions about this advisory, please contact FileCloud support.