|
Severity factors |
7 High, 6 Medium, 3 Low, as rated by Node.js. None is exploitable in FileCloud. |
|
Affected Component |
Node.js runtime (bundled with FileCloud) |
|
Status |
Not exploitable – no action required |
|
Versions affected |
FileCloud versions up to and including 23.263.3 bundle an affected Node.js version |
|
Version fixed |
FileCloud version 23.264 (due December 2026), which bundles Node.js 24.22.3 |
Description
On 11 November 2026, Node.js released fixes for 16 vulnerabilities in Node.js 24.x (7 High, 6 Medium, 3 Low). They are fixed in Node.js 24.22.3. FileCloud bundles Node.js 24.x; vulnerability scanners will report the bundled version as affected.
FileCloud's product security team has verified that FileCloud Server is not exploitable through any of these vulnerabilities, as each one needs a Node.js feature that FileCloud does not use. No action is required. FileCloud 23.264 updates the bundled Node.js to 24.22.3, after which scanners stop reporting it.
Affected Versions / Scope
-
Node.js version: 24.x before 24.22.3 (as bundled with FileCloud), on Windows and Linux
-
FileCloud 23.263.3: Node.js 24.22.1
-
FileCloud 23.263.0 to 23.263.2: Node.js 24.18.1
-
CVEs: CVE-2026-123863, CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-126051, CVE-2026-123872, CVE-2026-123874 (High); CVE-2026-123828, CVE-2026-123867, CVE-2026-123868, CVE-2026-123871, CVE-2026-123877, CVE-2026-123875 (Medium); CVE-2026-123829, CVE-2026-123862, CVE-2026-106071 (Low)
Impact
Each of the 16 vulnerabilities needs one of the following:
-
Node.js running an HTTP/2 server, including respondWithFile() or altsvc(): CVE-2026-123863, CVE-2026-123865, CVE-2026-123866, CVE-2026-123874, CVE-2026-123828, CVE-2026-123868, CVE-2026-123875
-
Node.js terminating TLS itself (an HTTPS server, SNI callbacks or per-host client certificates): CVE-2026-123864, CVE-2026-126051, CVE-2026-123872, CVE-2026-123867
-
An HTTPS client agent that mixes the default CAs with an empty CA list: CVE-2026-123877
-
A proxy URL with credentials configured for Node.js: CVE-2026-123871
-
Calling zlib's params() on a live stream: CVE-2026-123862
-
Running Node.js with the --permission flag: CVE-2026-123829, CVE-2026-106071
FileCloud uses none of these. Node.js runs only three FileCloud services: the push notification service and the DRM viewer service, which serve plain HTTP/1.1 WebSocket connections behind Apache, and a message queue worker that has no network listener. Apache terminates all TLS, no proxy is configured for Node.js, and neither FileCloud nor the WebSocket library it uses calls zlib's params(). FileCloud does not run Node.js with the --permission flag.
What you should do to fix this vulnerability
FileCloud Server admins:
No action is required now. FileCloud is not exploitable through these vulnerabilities, so no configuration change is needed. When FileCloud 23.264 is released (due December 2026), upgrade to it to update the bundled Node.js to 24.22.3.
To check the bundled Node.js version
-
Run
node -vwith the Node.js that FileCloud installed. On Linux,which nodeshows which Node.js is in use.
-
A version below 24.22.3 is expected until you upgrade to 23.264. Vulnerability scanners will report it against these CVEs, but it is not exploitable in FileCloud.
Notes / Caveats
-
This assessment covers the Node.js services shipped with FileCloud Server on Windows, RHEL and Ubuntu. It does not cover other Node.js applications installed on the same server; check those against the Node.js advisory.
-
After the upgrade to 23.264,
node -vreports 24.22.3.
References
-
Node.js: November 2026 security releases – https://nodejs.org/en/blog/vulnerability/november-2026-security-releases
-
Node.js 24.22.3 release – https://nodejs.org/en/blog/release/v24.22.3
FileCloud Online Admins
No action is required. FileCloud Online is not exploitable through these vulnerabilities, for the same reasons. FileCloud will update hosted servers to Node.js 24.22.3 with FileCloud 23.264.
If you have any questions about this advisory, please contact FileCloud support.