CVE-2026-114938 (Java4Shell)
TL;DR
- If you use a cloud instance, you are unaffected. You do not need to take any action.
- Exploitation requires an authenticated user or network access to trigger a connection to an attacker-controlled server, and the flaw is only active on x86-64 CPUs with AVX-512 VBMI. arm64, Graviton, and older x86-64 hardware without this instruction set is not affected.
- Self-hosted customers should update to get the fix, or apply the interim mitigation below.
Affected components
Java-based Retool database connectors.
| Resource type | What it connects to | Driver or SDK |
|---|---|---|
| databricks | Databricks SQL Warehouse | Databricks JDBC driver (com.databricks.client.jdbc.Driver) |
| databricksLakebase | Databricks Lakebase (Postgres) | Postgres JDBC (org.postgresql.Driver) |
| motherduck | MotherDuck (hosted DuckDB) | DuckDB JDBC (org.duckdb.DuckDBDriver) |
| kafka | Kafka | Apache Kafka clients |
| sqs | AWS SQS | AWS Java SDK |
| sns | AWS SNS | AWS Java SDK |
| jdbc (Hive only) | Apache Hive | Hive JDBC (org.apache.hive.jdbc.HiveDriver) |
What's affected
- The database connector running on x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake and later, AMD Zen 4 and later).
- Not affected: JDBC connectors other than Hive, which run Java 11.
- Applies only when you self-host.
Am I affected?
If you self-host, you are affected if your instance runs the database connector on x86-64 hardware with AVX-512 VBMI. Instances on arm64/Graviton, or older CPU architectures without this instruction set, like Intel Cascade Lake, are not affected. Intel Ice Lake and later include AVX-512 VBMI, so they are affected.
Impact
The reliable outcome of exploitation is a crash of the database connector process. Remote code execution was demonstrated in sample Spring Boot applications, but there is no universal exploit known at this time.
Exploitation requires initiating a connection to a maliciously controlled server. For Retool, this means an authenticated user or network access to the instance.
Mitigations
Cloud instance: No action is required. The mitigation is already in place.
Self-hosted:
- Update to the patched version for your release line: 4.0.30, 4.34.19, or 4.86.1.
- If you cannot update immediately, set
JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsicson all Retool containers or pods. The variable takes effect only after you apply it. Where you set it depends on how you deployed:- Helm. Add the variable to your
values.yaml, then runhelm upgrade. - Docker Compose. Add the variable to
docker.env, then runsudo docker compose up -d. - Terraform blueprints. Set the variable in
retool_helm_extra_valuesinmain.tf, then runterraform apply. Editing Helm values directly on a blueprint-managed instance is overwritten by the next apply.
- Helm. Add the variable to your
Customers on versions older than 4.x should note that these versions are end-of-life and do not receive backported security fixes. Upgrade to a supported 4.x version as soon as possible.
Affected and patched release versions
Patches are available for each supported self-hosted 4.x release line.
| Channel | Affected version | Patched version |
|---|---|---|
| Self-hosted 4.0 | 4.0.0 to 4.0.29 | 4.0.30 |
| Self-hosted 4.34 | 4.34.0 to 4.34.18 | 4.34.19 |
| Self-hosted 4.86 | 4.86.0 | 4.86.1 |
| Earlier than 4.x | End of life, no backported fix | Upgrade to a supported 4.x version |
References
Revision history
- 2026-11-18: Initial publication.