---
title: "Java4Shell on OpenSearch and Elasticsearch"
author: "Max Irwin"
date: 2026-11-18
canonical_url: https://bonsai.io/blog/java4shell-on-opensearch-and-elasticsearch/
license: CC BY-SA 4.0
license_url: https://creativecommons.org/licenses/by-sa/4.0/
copyright: Bonsai.io, 2026
---

We recently investigated the impact of the “[Java4Shell](https://calif.io/java4shell)” vulnerability (CVE-2026-1149) and we determined no direct exposure in the Bonsai platform. Our defense in depth created a shield from this specific issue, but we will of course be pursuing updates to all components that could be affected, if even they are not accessible for an exploit.

The vulnerability is found in Java applications in specific circumstances:

-   Running on x86-64 architecture processors of a specific generation (Intel Xeon: Ice Lake, Sapphire Rapids, Emerald Rapids, Granite Rapids; AMD EPYC and Ryzen: Zen 4 or newer)
-   Running Java version 17 or above

## x86 vs ARM

Over the past year, we've migrated most of our fleet to ARM64 because they're more performant than x86, and at a better price point. During this process, we ran [intensive benchmarks](https://bonsai.io/blog/java4shell-on-opensearch-and-elasticsearch/@blog/how-to-really-benchmark-search-engines/index.md) against lexical, vector, and hybrid search use cases, proving to ourselves the value of ARM64 for search workloads.

As ARM64 is not vulnerable to this exploit, those clusters are safe even though they run newer JVM versions.

## Defense in depth

We run a proprietary proxy as the public face of our platform, in front of all search traffic served by Bonsai, which was also not affected by the Java4Shell vulnerability. This proxy helps, among other duties, to provide an extra shield for incoming traffic, managing and authenticating every OpenSearch and Elasticsearch request we serve.

We also use many additional security defense and scanning tools, including peered VPCs, private subnets, and tools that actively scan our code and running applications on an ongoing basis.

The constant evolution of our platform toward one that is significantly more secure, patchable, and robust is part of the managed search guarantee that we provide to our customers.

## Status updates

You can find current details on this or any other incident on our [status page](https://status.bonsai.io/), and as always, customers can write into our customer support to receive tailored information to their particular use case.

Thank you for continuing on this search journey with us.

_Copyright ©️ Bonsai.io, 2026 · By Max Irwin · Originally published at https://bonsai.io/blog/java4shell-on-opensearch-and-elasticsearch/ · CC BY-SA 4.0_
