
On 17 November 2026 a vulnerability in the Java runtime became public: CVE-2026-114938, known as Java4Shell. It is a memory corruption bug in the accelerated Base64 decoder of the Java virtual machine. The bug is in Java, not in GeoServer, MapStore, GeoNode, GeoNetwork or CKAN, but every server application that runs on an affected Java inherits it.
The good news is that the mitigation is simple, safe and quick. This post gives the short answer first, then the details for each product, then the technical background for those who want it. Everything below marked as tested was verified in our lab on 18 November 2026.
The short answer
- Check which Java each of your services runs on. It depends on the version of the product you have and on how it was installed (see "Product by product").
- Add one Java option to every Java 11 or newer runtime, then restart:
-XX:-UseBASE64Intrinsics - Check that the running process picked it up with
jinfo(see "How to verify"). - If your Java is on the affected list, update it when your vendor publishes the fixed build. The option can stay in place afterwards.
Java 8 is the only exception. Standard Java 8 needs nothing and must not get the option. The one affected Java 8, a commercial Oracle product, needs a Java update. See "Java 8" below.
The option only tells Java to use its regular Base64 decoder instead of the accelerated one. Applications, configuration and data are untouched.
The situation in brief
- What it is. An out-of-bounds write in the hand-optimised Base64 decoding routine that Java uses on some processors. A crafted Base64 string makes it write a few bytes beyond its buffer.
- Who is affected. According to the public reports, a system is affected only when both conditions are true:
- Java: Java 17.0.6 or newer, Java 21, Java 25 or Java 27, from any OpenJDK based distribution. For Java 8, only the commercial Oracle Java 8 Enterprise Performance Pack (Oracle lists build
8u511b33-perf); - Processor: x86-64 with the AVX-512 VBMI instruction set, such as recent Intel Xeon generations and AMD Zen 4 or newer.
- Java: Java 17.0.6 or newer, Java 21, Java 25 or Java 27, from any OpenJDK based distribution. For Java 8, only the commercial Oracle Java 8 Enterprise Performance Pack (Oracle lists build
- Why it matters for web applications. Base64 carries login headers and tokens, so the decoder often runs before a user is authenticated.
- Severity. Oracle rates it 8.1 (CVSS 3.1) and describes it as difficult to exploit. The researchers who found it rate it 9.2 (CVSS 4.0).
The affected list is recent and may still change. For this reason the rule is the same for every Java version except Java 8, in line with the guidance being prepared by the GeoServer project:
| Your Java | On the affected list today | What to do |
|---|---|---|
| Java 17.0.6 or newer, 21, 25, 27 | Yes, on processors with AVX-512 VBMI | Add the option, then update Java when the fix is available |
| Java 11, Java 17.0.0 to 17.0.5, any other release from Java 11 up | No | Add the option as a precaution. It is accepted without side effects (tested on Java 11 and 17.0.5) |
| Standard Java 8 | No | Do nothing. Do not add the option, Java would not start |
| Oracle Java 8 Enterprise Performance Pack | Yes, on processors with AVX-512 VBMI | Update Java following the Oracle advisory |
The processor does not change what to do: the rule depends only on the Java version.
Product by product
| Product | Java involved | Where the option goes |
|---|---|---|
| GeoServer | Yes | The GeoServer JVM |
| GeoWebCache standalone | Yes | Its own JVM |
| GeoFence standalone | Yes | Its own JVM |
| MapStore | Yes | The MapStore JVM |
| GeoNode | Yes, through its GeoServer | The GeoServer that comes with GeoNode |
| GeoNetwork | Yes, and in Elasticsearch where used | The GeoNetwork JVM and Elasticsearch |
| CKAN | Yes, through Solr | Solr |
Whether the option applies depends on the Java version, not on the product. There is no single GeoServer, MapStore, GeoNode, GeoNetwork or CKAN. Every installation has its own product version, and each version and each kind of installation (Docker image, binary package, WAR in your own Tomcat, operating system packages) comes with its own Java. So the first step is always the same: find out which Java your service runs on, then apply the rule by Java version above.
To find it on Linux, readlink -f /proc/PID/exe shows the Java binary of the running process. Run that binary with -version (tested). In Docker and Kubernetes, run the same commands inside the container.
Where we name a Java version below, it is what we found on the specific version we checked on 18 November 2026. It is not a statement about every installation of that product.
GeoServer
- GeoServer is affected when it runs on an affected Java. Which Java that is depends on your GeoServer version and on how it was installed: check it and apply the rule above. Where the option applies, add it also when all the services are public and anonymous.
- What we checked: the definitions of the official GeoServer 3.0 Docker image and of the GeoSolutions GeoServer Docker image both use Eclipse Temurin 21. Other versions, older tags and other kinds of installation can run on a different Java.
- Tomcat: add
CATALINA_OPTS="$CATALINA_OPTS -XX:-UseBASE64Intrinsics"tobin/setenv.sh(tested on Tomcat 9). - Docker and Kubernetes: set the environment variable
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsicson the container. If the variable already has a value, append to it. - The GeoWebCache embedded in GeoServer and the GeoFence plugin run inside the GeoServer JVM and are covered by the same option. A standalone GeoWebCache or GeoFence has its own JVM: check its Java in the same way.
MapStore
- MapStore is affected when it runs on an affected Java. Which Java that is depends on your MapStore version and on how it was installed: check it and apply the rule above.
- What we checked: the MapStore 2026.02.03 binary package ships Eclipse Temurin 17.0.13, and the current definition of the MapStore Docker image uses Java 17. Other versions can run on a different Java.
- Docker image: set
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsicson the container. - Binary package: it ships its own Java runtime, inside the package. That is the Java to check, not the one installed on the server. Then create or edit
bin/setenv.shwithCATALINA_OPTS="$CATALINA_OPTS -XX:-UseBASE64Intrinsics"and restart (tested on 2026.02.03). - WAR in your own Tomcat: the Java is the one your Tomcat uses. Same
setenv.shline. - The printing module, where installed, runs in the same JVM and is covered by the same option.
GeoNode
- GeoNode itself is a Python (Django) application and is not affected. The Java component is the GeoServer that comes with it.
- Which Java that GeoServer runs on depends on your GeoNode version and on how it was installed: check it and apply the rule above.
- What we checked: the current GeoNode Docker setup, which comes with GeoServer 2.28.x, uses Java 17 for GeoServer. Other GeoNode versions come with other GeoServer versions and can run on a different Java.
- Where the option applies, add
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsicsto the environment of the GeoServer service (geoserverin the standard Docker Compose setup) and recreate the container.
GeoNetwork
- GeoNetwork is affected when it runs on an affected Java. Which Java that is depends on your GeoNetwork version and on how it was installed: check it and apply the rule above.
- What we checked: the official GeoNetwork 4.4.12 Docker image uses Java 11, the official 4.2.17 and 3.12 images use standard Java 8. Neither is on the affected list. Other versions and installations outside Docker can run on a different Java.
- On standard Java 8 nothing is needed and the option must not be added (see "Java 8").
- GeoNetwork 4 works with Elasticsearch, which ships its own Java. Which one depends on the Elasticsearch version. Public research lists Elasticsearch among the affected products. The same rule applies: add the option through the Elasticsearch JVM options file, as described in the Elastic documentation, and keep Elasticsearch reachable only from GeoNetwork.
CKAN
- CKAN itself is Python and is not affected. The Java component is Apache Solr.
- Which Java Solr runs on depends on your Solr version and on how it was installed: check it and apply the rule above.
- What we checked: the official Solr 9.10 and 9.11 Docker images are built on Eclipse Temurin 17, and the CKAN Solr 9 images are built on the official Solr 9 images. Other Solr versions run on a different Java.
- Where the option applies, add it through
SOLR_OPTS, insolr.in.shor as an environment variable of the Solr container:SOLR_OPTS="$SOLR_OPTS -XX:-UseBASE64Intrinsics". - As usual, Solr must be reachable only from CKAN, never from the public network.
Java 8
Only one kind of Java 8 is affected: the Oracle Java 8 Enterprise Performance Pack, a commercial product. Every other Java 8, called standard Java 8 in this post, is not affected. The two need opposite actions.
| Standard Java 8 | Oracle Java 8 Enterprise Performance Pack | |
|---|---|---|
| What it is | The usual Java 8: Eclipse Temurin, the OpenJDK 8 packages of Linux distributions, the standard Oracle Java 8 | A commercial Oracle build of Java 8 with newer performance code. Its build name ends in -perf |
| Affected | No. It does not contain the accelerated decoder | Yes. Oracle lists build 8u511b33-perf and says earlier builds are likely affected too |
| What to do | Nothing for this issue. Do not add the option: Java stops at startup with Unrecognized VM option 'UseBASE64Intrinsics' (tested on Eclipse Temurin 8) |
Update Java following the Oracle advisory. The reported fixed build is 8u513-perf |
Two practical notes for standard Java 8, both tested:
- If the option arrives through
JAVA_TOOL_OPTIONS, every Java command started in that environment stops in the same way, not only the server. - If one configuration has to serve both standard Java 8 and newer runtimes, put
-XX:+IgnoreUnrecognizedVMOptionsbefore the option. Standard Java 8 then starts and ignores it.
How to verify
Ask the running JVM. jinfo is part of every JDK:
jinfo -flag UseBASE64Intrinsics PID
PID is the process id of the Java process. For Tomcat on Linux, for example: jinfo -flag UseBASE64Intrinsics $(pgrep -f org.apache.catalina.startup.Bootstrap | head -1)
-XX:-UseBASE64Intrinsics(minus): the option is active.-XX:+UseBASE64Intrinsics(plus): the option is missing. Check the startup options and restart.
Practical notes, tested in our lab:
- Run it as the user that owns the Java process, or as root.
- The runtime is a JRE without
jinfo? Usejinfofrom any JDK 11 or newer. It does not have to be the same version or vendor, and an unpacked JDK archive is enough. Some Docker images are built on a JRE: among those we checked, the official Solr and GeoNetwork images. - When the option comes from
JAVA_TOOL_OPTIONS, Java also writesPicked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsicsat the top of its output. With Tomcat this line is incatalina.out. - Looking for the option in the process command line or environment is a useful first look, not a proof. Options can also come from files, and a later setting can override an earlier one. When in doubt,
jinfodecides.
An HTTP test from outside cannot confirm the mitigation. In our tests a mitigated server and an unmitigated one answered a malformed header in exactly the same way. Please do not point public proof-of-concept tools at production systems: they tell you nothing reliable and can damage a vulnerable server.
The permanent fix
- The fix is a Java update. The fixed OpenJDK versions reported so far are 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1. According to public reports, Oracle and Amazon Corretto have already published them.
- When we checked on 18 November, Eclipse Temurin, the Java of the Docker images we checked, had not published fixed builds yet. Rebuilding an image on the same base does not fix the issue until the base is updated.
- Check the full version string. The fixed builds add a further digit to the October versions:
17.0.21alone is not the fixed one. - Updated GeoSolutions Docker images with the option already set are being released. We will update this post with the details.
Technical details
For readers who want to know what is behind the recommendation.
- Root cause. On processors with AVX-512 VBMI, the HotSpot JIT compiler replaces the Java loop of
java.util.Base64decoding with a hand-written assembly routine. In the handling of the padded tail of the input, a mask is computed wrongly and a full-width vector store writes about 62 bytes past the end of the output, before the input is rejected as invalid. - Scope inside Java. Only the basic and URL decoders of
java.util.Base64use the routine, and only after the JIT has compiled them. Libraries with their own Base64 implementation do not reach it. - What the option does.
UseBASE64Intrinsicsis a standard product flag of HotSpot. Switched off, the JVM keeps the plain Java implementation.-XX:UseAVX=2also closes the path, but it disables every AVX-512 optimisation and is reported not to start on ARM, so we do not recommend it. - Performance. In the versions of these products that we reviewed, Base64 decoding is used mainly for authentication and small payloads, not for rendering or tiling. We expect no measurable change. We have not benchmarked it.
What we tested, on an x86-64 host with AVX-512 VBMI:
| Runtime | Default options | With the option |
|---|---|---|
| Eclipse Temurin 17.0.21 | Out-of-bounds write reproduced | Not reproduced |
| Eclipse Temurin 21.0.13 | Out-of-bounds write reproduced | Not reproduced |
| Ubuntu OpenJDK 21.0.13 | Out-of-bounds write reproduced | Not reproduced |
| Eclipse Temurin 17.0.13, bundled in the MapStore 2026.02.03 binary package | Out-of-bounds write reproduced | Not reproduced |
| Eclipse Temurin 17.0.5 | Not reproduced | Option accepted |
| Eclipse Temurin 11.0.25 | Not reproduced | Option accepted |
| Eclipse Temurin 8u512 (standard Java 8) | Not reproduced | Java does not start |
The test is a small program that runs in a separate, throwaway JVM and checks whether the decoder writes beyond the bytes it is entitled to. It never touches the running service.
On a MapStore 2026.02.03 lab server we also observed that:
- without diagnostics, an unmitigated server showed no visible symptom when it received malformed headers, which is why a quiet server proves nothing;
- with JVM heap verification enabled, the unmitigated server stopped on a heap integrity error under the same traffic, while the server with the option handled it without any effect.
Security is ongoing work for us
GeoSolutions leads the development of MapStore and takes part in the security work of the GeoServer and GeoNode projects. When an issue like this appears, we analyse it on the real products, test the mitigations and share what we find with the communities. We are certified ISO 27001.
How we can help
Running open source in production does not mean running it alone. With our Enterprise Support Services, Enterprise Subscription Services and Professional Training Services we help organisations:
- understand whether an installation is exposed, and verify it after the mitigation
- apply the option and plan the Java update across environments
- review deployments, including the components around the maps
- train their teams
Customers with an active support contract are being contacted directly and can open a ticket at any time. Want to talk about your GeoServer, MapStore, GeoNode, GeoNetwork or CKAN installation? Write to sales@geosolutionsgroup.com.
This post is general guidance on the products as published. It is not an assessment of any specific installation.
Keep an eye on this post. We will update it as new information becomes available, for example fixed Java builds, updated Docker images and changes to the list of affected versions. Last update: 18 November 2026.
If you are interested in learning more about how we can help you achieve your needs with GeoServer, MapStore, GeoNode and GeoNetwork through our Enterprise Support Services, Professional Training Services and Subscription Services please contact us!
The GeoSolutions team


O que você vai aprender?
Instalação e configuração do GeoNode 5.1
Quando?
Horário: 19h às 22h (Brasília)
Modalidade: EAD ao vivo
Carga horária: 18 horas (6 aulas)
Gravações disponíveis por 12 meses
Certificado de participação
Instrutor: Fernando Quadro
Inscrições até 30/11/2026!
Garanta sua vaga:
Transforme seus conhecimentos em GIS e dê o próximo passo na publicação e gestão de dados geoespaciais na web!





”. He told the story of a project that left these mountains and found its way to fieldwork sites on every continent. He also shared where it is heading next, with on-the-fly project creation, COGO tools, NTRIP support for RTK accuracy and 3D data collection.








Our lead QField developer celebrated his birthday with all the ninjas singing around a raclette in a mountain chalet.
And some squatted and climbed their way to the perfect portraits for our website, because dedication to the shot is a team sport. 








It was a happy mix of laptops, coffee and the kind of quick conversations that are so much easier in person. A question that might take a day of back and forth over chat gets settled in ten minutes at a shared table. We also set aside time to talk about how we work together and where we want to go next, filling a few walls with sticky notes along the way. When heads needed clearing, the football table saw some fiercely competitive matches.















Figure1: Overlay of Elbe D2KP workflow outputs with HQ100 flood hazard zones using the QGIS tool integrated into the AquaINFRA Virtual Research Environment (VRE). The map displays two vector layers: the subbasin population density layer generated by the Elbe D2KP workflow and the HQ100 flood hazard layer for Brandenburg.
Figure 2 . A well-connected Fuzzy Cognitive Map (FCM) developed by AquaINFRA partners during the workshop in Oslo, Norway.
Figure 3: Fuzzy Cognitive Map (FCM) developed with water management practitioners from Emschergenossenschaft during the workshop in Germany.




Empowering Conservation Through Open Technologies with 52°North and PEOPLE-ECCO
Figure 1: Early Adopters and their regions
Figure 2: High-level architecture of the PEOPLE-ECCO platform
Figure 3: User Interface of the PEOPLE-ECCO platform
User Handbook: Read the operational guidelines and workflow explanations in the
Project Results Browser: Inspect actual demonstration site results via the
Official Website: Visit the









