Java4Shell (CVE-2026-114938) and PHP Security Release (CVE-2026-115560)
FileCloud Online customers need to do nothing: FileCloud has already applied the fixes. FileCloud Server (self-hosted) customers may need a short check or interim step until FileCloud 23.264 ships in December 2026.
|
Your deployment |
Java4Shell (CVE-2026-114938) |
PHP release (CVE-2026-115560 and others) |
|---|---|---|
|
FileCloud Online |
No action. Fix already applied. |
No action. |
|
Server 23.263.3, default PHP settings |
Action needed only if Content Search is enabled |
No action. Not exploitable with default settings. |
|
Server earlier than 23.263.3 |
Action needed only if Content Search is enabled |
Turn off session upload progress (see below) |
|
Server with Content Search disabled |
Not affected. On Linux, still install the OS Java update. |
As above, by version |
The permanent fix for both is FileCloud 23.264, due December 2026. It bundles a patched Java 25 and PHP 8.5.13.
Java4Shell (CVE-2026-114938)A FileCloud Server (up to and including 23.263.3) is affected only if Content Search (Solr) is enabled, runs on Java 17.0.6 or later without the November 2026 security update (on Windows, this includes the bundled OpenJDK 26.0.1), and the server CPU supports AVX-512 VBMI. Java4Shell is a memory corruption flaw in Java's Base64 decoder, fixed by OpenJDK and Oracle on 17 November 2026. In FileCloud, a user who uploads a crafted file can trigger it. The most likely result is a Content Search crash, but remote code execution cannot be ruled out.
Not affected:
- Servers with Content Search disabled
- Document Converter (document preview)
- ARM64 servers and x86-64 CPUs without AVX-512 VBMI (Intel before Ice Lake, AMD before Zen 4)
Content Search only accepts connections from the FileCloud server itself, so the risk comes from uploaded files, not direct network access.
Check whether Content Search is running
Windows:
C:\xampp\java\bin\java -version netstat -an | findstr :8983
Linux:
ss -ltn | grep 8983 java -version
If nothing is listening on port 8983, Content Search is not running and the server is not exposed.
What to do
- Linux: Install your operating system's OpenJDK security update now, then restart Content Search and the Document Converter. On RHEL, run the Java update with
--disablerepo='filecloud-*', because the FileCloud repository pins the Java version. If you can't install the update yet, apply the interim -XX:-UseBASE64Intrinsics setting in /etc/default/solr.in.sh instead (see the advisory, Step 4). - Windows: Add
-XX:-UseBASE64Intrinsicsto Content Search's startup options inC:\xampp\solr\bin\solr.in.cmd, then fully restart Content Search. Upgrade to 23.264 when released. - Can't apply either yet: Stop Content Search until you upgrade. Search won't return results while it's stopped.
- Self-managed Java (for example, from jdk.java.net): Replace it with a patched build from a vendor that ships security updates. Don't downgrade Java.
Step-by-step commands, verification and HA/multitenant notes are in Advisory 2026-11/04.
PHP security release (CVE-2026-115560 and others)
None of the 14 PHP vulnerabilities can be exploited on a default FileCloud 23.263.3 server. PHP released fixes on 19 November 2026 and rates the most serious critical (CVSS 9.2), but each needs a non-default configuration or an uncommon setup. FileCloud reviewed every one:
|
Vulnerabilities |
Why FileCloud is not exposed by default |
|---|---|
|
Session issues: CVE-2026-115560, CVE-2026-126714, CVE-2026-129481 |
They rely on |
|
Timezone cache: CVE-2026-129496 |
Needs a PHP build that logs startup errors to a file. FileCloud's defaults don't. |
|
PHP-FPM / PHP-CGI: CVE-2026-129289, -129291, -129292, -129538 |
FileCloud runs PHP inside Apache, which is not affected. |
|
Others: CVE-2026-128064, -127960, -128090, -129501, -129506, CVE-2026-15353 |
Need PHP features FileCloud doesn't use (PHAR, SOAP server, new DOM API) or a connection to an attacker's server. |
Vulnerability scanners will still flag FileCloud 23.263.3, because it bundles PHP 8.4.27, which is in the affected range.
What to do
- 23.263.3 with default PHP settings: Nothing.
- Earlier than 23.263.3, or PHP settings changed: Make sure
session.upload_progress.enabledis Off in thephp.iniApache uses, and that FileCloud's.htaccessdoesn't override it. On Linux,error_logshould have no value. Then restart Apache. - High availability: Apply on every web/app node, restarting Apache one node at a time.
Quick check on Windows (the first line should show Off, the second nothing):
C:\xampp\php\php.exe -c C:\xampp\php\php.ini -i | findstr "session.upload_progress.enabled" findstr "session.upload_progress" C:\xampp\htdocs\.htaccess
Linux commands for Ubuntu and RHEL are in Advisory 2026-11/05.
FAQ
Our vulnerability scanner flags FileCloud's PHP or Java. Are we exposed? Scanners match on version numbers. FileCloud 23.263.3 bundles PHP 8.4.27, and on Windows OpenJDK 26.0.1, so both will be reported. For PHP, a default 23.263.3 server is not exploitable. For Java, exposure depends on Content Search and your CPU (see above). The flags clear once you're on 23.264.
Can I upgrade PHP myself? No. FileCloud is tested with the PHP version it bundles, and other versions may break it. Use the interim settings above and upgrade to 23.264.
Can I upgrade Java myself? On Linux, yes: install your OS vendor's OpenJDK security update. On Windows, use the interim setting and wait for 23.264, which bundles a patched Java 25. If you installed and manage Java yourself, replace it with a patched vendor build; don't downgrade.
When is 23.264 available? It is due in December 2026. It includes both fixes.
Does the interim Java setting affect performance or features? It turns off an optimized Base64 code path. Search and previews keep working. Very Base64-heavy workloads may run slightly slower.
Is document preview affected? No. The Document Converter never passes uploaded content to the vulnerable decoder. Applying the Java setting to it is optional.
Will disabling public upload links protect us from Java4Shell? It reduces exposure but doesn't remove it. Any user who can upload a file can trigger the issue while Content Search is enabled.
We have HA or a separate Solr server. Where do we apply the steps? Java4Shell: on every Solr server, one at a time, confirming search works before moving on. PHP: on every web/app node, restarting Apache one node at a time. In multitenant setups, once per server covers all tenants.
Has either issue been exploited? No exploitation of Java4Shell was known as of 17 November 2026. PHP's issues require non-default setups that FileCloud doesn't use by default.
When to contact support
Contact FileCloud support if Content Search won't start after adding the Java setting, the Linux Java update doesn't show the CVE fix, or your PHP check shows a value you can't change. Include your FileCloud version, OS, and the output of the check commands above.