In short
On 17 November, security firm Calif disclosed a serious flaw in Java, tracked as CVE-2026-114938 and nicknamed Java4Shell. It is not a flaw in our systems, or in FileMaker or Claris software as such. It is in Java, a third-party language and runtime that is used almost everywhere. We are not aware of any attacks using it. We are checking every server we manage anyway, and we will contact any client individually if their systems are exposed.
What the issue is
Java is the software that runs behind a large share of business applications, from build tools to identity systems. Java4Shell is a memory-corruption bug in the part of Java that decodes Base64, a common way of packaging data for transfer. If an attacker can get specially crafted data to that decoder, they may be able to run their own commands on the server without logging in. Calif rates it 9.2 out of 10 (CVSS 4.0), which is critical.
Because the flaw sits in Java itself, it isn't down to how any one organisation built or configured its software. Calif reports testing it against widely used products including Jenkins, Jira, Confluence, Keycloak and JFrog Artifactory. Those are examples of software that runs on Java, not products that are at fault.
How it was found
Like PHP2Shell, the PHP vulnerability disclosed a few weeks ago, Calif says this one was found with AI assistance. Its researcher used an AI coding tool to review part of Java's compiler and spot the flaw. Public reporting on PHP2Shell is clear that people still steered the work, with AI doing much of the heavy lifting. The practical point is that AI tools are making it faster and cheaper to find bugs like this, and that works for defenders and attackers alike. Expect more disclosures like it. We wrote about the same shift in how AI-assisted bots find and attack FileMaker Server.
Who is affected
As reported so far, the flaw affects OpenJDK 17.0.6 and later, which includes Java 17, 21, 25 and 27 from vendors such as Oracle, Amazon Corretto, Eclipse Temurin, Red Hat and Microsoft. Two conditions narrow the exposure. The server needs an x86-64 processor with a feature called AVX-512 VBMI, and attacker-controlled data has to reach the vulnerable code. ARM-based Java installs aren't affected. Java 8 and 11 are reportedly unaffected, though we'd treat that as unconfirmed until vendors say so.
That is why we think it is more obscure than the PHP issue, which touched a far larger share of the web. It still isn't rare. Many Intel Xeon and AMD EPYC cloud servers have the processor feature.
Why this matters if you use FileMaker
FileMaker's database engine does not run on Java, so a server that only serves FileMaker Pro and FileMaker Go clients is not running the affected code. The exception is the Web Publishing Engine. Claris's security guide says FileMaker WebDirect and Custom Web Publishing need a Java runtime, and that on Windows and macOS you install OpenJDK yourself when you turn those features on. On Linux the FileMaker Server installer puts it there for you, and in FileMaker Cloud, Claris does.
The versions in play are the affected ones. FileMaker Server moved to Java 17 with the 2023 release, and the FileMaker Server 2026 release notes (version 26.0.1, June 2026) add support for JDK 21 for the runtime behind WebDirect. The 26.0.3 notes mention the Temurin OpenJDK 21 build specifically. Any FileMaker Server with WebDirect or Custom Web Publishing enabled on an x86 processor is therefore running a Java in the range Calif describes, 17.0.6 or later, unless it has been updated to a fixed build since 17 November.
Three things narrow it for FileMaker users. A server with the Web Publishing Engine switched off isn't running Java, even if it is installed. An ARM server, including Apple silicon Macs, isn't affected. And nobody has yet shown that the data a browser sends to WebDirect can reach the vulnerable decoder. Until someone does, we are treating every internet-facing WebDirect server on an Intel or AMD processor as exposed, and those are first in our checks above.
We have not seen a statement from Claris on this flaw as of 19 November. Because FileMaker Server uses a Java you install yourself on Windows and macOS, you don't need to wait for a FileMaker update to patch it. The fixed builds are an OpenJDK update, applied through the Connectors panel in Admin Console on FileMaker Server 2024 and later. Check Claris's FileMaker Server and Java article for the minimum version your release supports before updating. If you host with us, we do this for you.
How we identify potentially exposed servers
We are going through every server we manage, including the FileMaker servers we host, and checking three things.
- Whether Java is installed, and which version. Java isn't listed in an application's own dependencies, so we check the servers directly.
- Whether the processor supports AVX-512 VBMI.
- Whether the server can be reached from the internet. Those go first.
What we know about attacks
We are not aware of any attacks using this flaw. Calif reports working exploits in its own testing, but none of the sources we've seen report attacks on real systems. The technical detail is due to be published after vendors' patches, and that can speed up attackers, so we are acting now.
What we're doing
- Checking all servers we manage, as above.
- Working with Claris and our other suppliers to confirm which of their products use Java and when fixes will be available.
- Applying vendor Java updates once we've confirmed they cover this flaw. Oracle released updates on 17 November, but not every report confirms that they include a fix for this CVE.
- Where an update isn't available yet, considering Calif's interim measure of starting Java with the setting
-XX:UseAVX=2, which switches off the affected code path. We will test that before using it. - Contacting any client individually if we find an exposed system.
This is the same approach we took during the October 2026 attacks on FileMaker servers: check everything we manage, fix what needs fixing, and tell the clients it touches directly.
If you run your own Java servers
Update to the latest build from your Java vendor and check the vendor's notes for CVE-2026-114938. If you can't update yet, ask your IT team about the interim setting above. Contact us if you'd like us to take a look.
Questions
If you have any questions, get in touch with us at support@neptunedigital.co.uk.
Sources