|
Vulnerability Type |
Outdated trusted certificate authority in CA bundle |
|
Severity factors |
This vulnerability is rated High (CVSS 3.1 base score 7.4) with a low likelihood of exploitation, which would require an attacker who is already able to intercept FileCloud's network traffic. There have been no confirmed reports of misuse. |
|
Versions affected |
All FileCloud Server versions up to and including 23.263.2, on Windows and Linux. |
|
Version fixed |
To be released (FileCloud 23.263.3) |
Description
In October 2026, the certificate authority eMudhra reported a key-generation issue affecting several of its intermediate certificates under the emSign ECC Root CA - G3 root. eMudhra revoked those certificates as a precaution. Browser and operating system vendors, including Mozilla, have since removed trust in this root.
FileCloud does not use eMudhra certificates. However, FileCloud includes a CA certificate bundle (cacert.pem) for its outbound HTTPS connections, such as connections to the license server, storage backends, and integrations. In affected versions, this bundle still lists the emSign root as trusted.
-
On Windows, FileCloud uses this bundle rather than the Windows certificate store, so Windows updates alone don't change it.
-
On Linux, some connections also use the operating system's CA store.
-
On Windows, the bundled Node.js runtime also has the emSign root in its built-in certificate list. This is updated by upgrading to FileCloud 23.263.3.
Updating the bundle (and, on Linux, the OS CA store) brings FileCloud in line with current browser and OS trust decisions.
Interim mitigation
FileCloud provides an updated cacert.pem file: https://zerg.codelathe.com/url/cdhqcg4xiszwfrib . It includes FileCloud-specific entries, so please use this file rather than a generic CA bundle.
Windows
-
Back up these files:
C:\xampp\htdocs\resources\certs\cacert.pem C:\xampp\htdocs\src\Core\cacert.pem -
Replace both files with the cacert.pem provided by FileCloud.
-
Open the FileCloud control panel, and restart the web server.
Note: Replacing cacert.pem updates the CA bundle used by FileCloud Server. The bundled Node.js runtime on Windows has its own built-in certificate list, which is updated when you upgrade to FileCloud 23.263.3. Therefore, we recommend that you upgrade to 23.263.3 once it is available.
Linux
-
Back up these files:
/var/www/html/resources/certs/cacert.pem /var/www/html/src/Core/cacert.pem -
Replace both files with the cacert.pem provided by FileCloud.
-
Apply the OS ca-certificates update:
# Ubuntu sudo apt update && sudo apt install --only-upgrade ca-certificates # RHEL sudo dnf update ca-certificates -
Restart the web server with:
# Ubuntu sudo systemctl restart apache2 # RHEL sudo systemctl restart httpd
Deployment notes for interim mitigation
Multitenant deployments: All tenants share the same installation, so the steps only need to be applied once.
High availability deployments: Apply the steps on every FileCloud web/app node. To avoid downtime, update and restart one node at a time.
FileCloud Online: No action is required. FileCloud will update hosted servers.
Fix
-
FileCloud Server up to and including 23.263.2: We recommend upgrading to 23.263.3 when it is released.
-
FileCloud Server on Linux: Apply your operating system's routine ca-certificates update.
-
FileCloud Online: No action is required.
If you have any questions about this advisory, please contact FileCloud support.