Status: Fixed in Validatar Cloud
Products reviewed: Validatar Cloud, Validatar Server, Data Agent
Customer action required: None for Validatar Cloud or the Data Agent. Validatar Server customers who run Apache Solr for Global Search should update Java on their Solr host.
Published: November 18, 2026
Java4Shell (CVE-2026-114938) is a flaw in the Java runtime, disclosed on November 17, 2026. Validatar is built on Microsoft .NET and does not run on Java, but Global Search does: it runs on Apache Solr, an open-source search engine that needs Java. Every Solr server in Validatar Cloud now runs on a Java runtime that contains the fix. Validatar Cloud customers do not need to do anything.
Validatar Server customers who use Global Search run Solr on their own hosts, on Java they installed. They should update Java on that host, as described under What you need to do, below.
About CVE-2026-114938
| CVE | Issue | Severity |
|---|---|---|
| CVE-2026-114938 | Memory corruption in the Java runtime's hardware-accelerated Base64 decoder when it reads crafted input | High (CVSS v3.1 8.1) |
Java4Shell affects Java 17.0.6 and later on x86-64 servers whose processors support AVX-512 instructions. That includes OpenJDK and the Java distributions built from it, such as Oracle Java SE, Eclipse Temurin, Amazon Corretto, Microsoft Build of OpenJDK, Azul Zulu and Red Hat's OpenJDK packages. Servers with ARM64 processors are not known to be affected.
An attacker who can send crafted Base64 data to a Java application on an affected server can corrupt the application's memory and may be able to take it over. The researchers who reported the flaw demonstrated it against several server products, Apache Solr among them. For Solr, the attacker must first be able to send requests to Solr itself.
Oracle released its fix on November 17, 2026, and the other Java vendors are releasing their own updates. The same day, CISA urged organizations to patch every Java installation, including Java bundled inside third-party applications and container images.
Where Validatar uses Java
Validatar Server, Validatar Cloud's application services and the Data Agent are .NET applications. Java appears in Validatar only in the search service behind Global Search, which is built on Apache Solr.
| Product | Runs Java | Status |
|---|---|---|
| Validatar Cloud | Yes, in the Global Search service (Apache Solr) | Fixed |
| Validatar Server (Windows and Linux) | Only on the Solr host you run for Global Search | Update Java on your Solr host |
| Data Agent | No | Not affected |
Validatar Cloud. Validatar did not wait for Apache to ship a Solr release with the fixed Java. Every server in Validatar Cloud's Global Search service, including the Apache ZooKeeper servers that coordinate Solr, has been rebuilt on a Java runtime that contains the fix. Solr itself is updated to version 9.11.0, the current release. Validatar finished this update on November 18, 2026.
Validatar Server. Validatar Server connects to Solr only when Global Search is set up. That Solr instance runs on a host you manage, on the Java installed there. This applies whether you installed Solr by hand or with a Validatar Linux install script, which installs Java only so that Solr can run.
Data Agent. The Data Agent does not include, install or call Java.
What you need to do
Validatar Cloud and the Data Agent: no action.
Validatar Server without Global Search: no action. If no Solr endpoint is set under Settings > Configuration > Global Search, Validatar Server does not use Solr.
Validatar Server with Global Search:
- On the host that runs Solr, install your Java vendor's update for CVE-2026-114938. The Solr download from Apache does not include Java, so Solr runs on whatever Java is installed on the host, for example Oracle Java SE, Eclipse Temurin, Amazon Corretto or your Linux distribution's OpenJDK package. Your vendor's security advisory names the fixed version.
- Restart Solr so it starts on the updated Java.
If you run Solr from a container image, the image carries its own Java. Move to a Solr image that includes the fixed Java as soon as one is published, or rebuild your image on a fixed Java runtime.
If you cannot update Java right away, the researchers list a workaround that turns off the affected code. Add the Java option -XX:-UseBASE64Intrinsics to SOLR_OPTS in Solr's include file (solr.in.sh on Linux, solr.in.cmd on Windows), then restart Solr.
Questions
Contact Validatar Support at support@validatar.com or through the support portal.
References
- CVE record: CVE-2026-114938
- NVD entry: CVE-2026-114938
- Oracle advisory: Critical Security Patch Update, November 2026
- CISA alert: Critical Java Vulnerability Requires Immediate Patching
- Researcher write-up: Java4Shell
Revision history
| Date | Change |
|---|---|
| November 18, 2026 | Initial publication |