Security advisory: update your Java runtime (Java4Shell)
A security vulnerability in some Java runtimes was publicly disclosed as CVE-2026-114938 ("Java4Shell"). On certain processors, a single crafted web request can crash or take control of the Java runtime of an application that decodes Base64 data. The Patchworks embedded report server decodes Base64 (in HTTP authentication), so installations meeting the conditions below are exposed.
Were you affected?
Your installation is potentially exposed if all of these are true:
- The Java runtime is in a vulnerable version range. Java 17, 21 and 25 releases older than the vendor’s fixed build (for Oracle Java 21, that is 21.0.13.1). Java 8 and Java 11 are not affected.
- The processor supports the AVX-512 VBMI instructions. This includes:
- Intel Ice Lake and newer Xeon processors,
- Intel 10th and 11th generation mobile and 11th generation desktop processors,
- AMD Zen 4 and newer processors.
- Firewall access was granted to Java. By default, the Windows Defender firewall blocks inbound connections from other machines, and this block applies to the report server. Access is typically granted by answering Allow to the Windows Defender prompt (“Allow Java to access these networks?”) when the application first started, or by a firewall rule added by your administrators. If no such rule exists, other machines could not reach the report server, even on a vulnerable runtime and CPU.
Where these conditions are met, both unprotected installations (no password file) and password-protected installations are reachable, because the authentication header itself is decoded with Base64.
What we have done
The current Patchworks release hardens the embedded report server:
- The report server now accepts connections from the local machine only, unless you explicitly enable network access (see below).
- Network access requires a password to be configured, and is refused when the Java runtime has not been updated.
- Requests are size-limited and time-limited, and all responses carry security headers.
What you should do
- Update Java now. Fixes are available now for Oracle Java (21.0.13.1) and Amazon Corretto (21.0.13.1.2). For Temurin, Zulu, Microsoft and other vendors, check your vendor’s status page or security advisory for the fixed build and when it will land, and install it as soon as it is available.
- Install the latest Patchworks release, which contains the hardened report server.
- If you view reports from other machines: add
httpd.bind_lan=trueto thepatchworks.inifile in your Patchworks user folder (usuallyDocuments/Patchworks), and configure a password by calling theaddUsermethod from a script that runs after the application starts (a PIN file, a script given as a program argument, or the scripting console). Note that passwords are sent in encoded clear text between machines; if access must be secure, put a TLS reverse proxy (such as Caddy or nginx) in front of the report server. - If you cannot update Java right away: as a temporary measure, add
-XX:-UseBASE64Intrinsicsto thelauncher.javaflagsproperty in thepatchworks.inifile (in your Patchworks user folder). This closes the Java4Shell issue until you are able to update. This is a stopgap, not a substitute for updating.
If you have questions or need help updating, contact support@spatial.ca.