SSB-2026-008 - Java4Shell vulnerability in OpenJDK (CVE-2026-114938)

CVSS score v3.1
Base 8.1
Temporal
Environmental

TLDR

Redeploy your Java application with a fresh build if it uses Scalingo’s standard JVM buildpack. For a custom Java runtime, select a vendor-fixed build before redeploying.

Scalingo for OpenSearch: Customer requests must be authenticated before they reach OpenSearch, which limits exposure. We plan to make the fix available by Tuesday, November 24, 2026. Once it is available, start the upgrade from the database dashboard.

Scalingo for Elasticsearch requires no customer action for this vulnerability.

Incident analysis

On November 17, 2026, OpenJDK and Java vendors published fixes for CVE-2026-114938, also known as Java4Shell. The flaw can allow remote code execution in applications running affected JVM builds. Exposure depends on the JVM build, processor features, and how the application handles untrusted data. Public proof-of-concept code is available. Upgrade affected runtimes as soon as possible. Oracle reports a CVSS 3.1 base score of 8.1. OpenJDK advisory · Red Hat advisory

What we did

On November 18, Scalingo updated its JVM buildpack. The updated buildpack lists fixed Azul Zulu JDK versions 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1 as defaults for their respective Java lines. Scalingo JVM buildpack release notes · Azul November 2026 release notes

We also applied security updates to some internal services identified as potentially affected.

What you should do

Java applications on Scalingo

  1. Check whether you need to change your Java configuration. If you pinned an affected JDK to an exact release, select a fixed build or use the corresponding major-version selector. Check java.runtime.version in system.properties, or JAVA_VERSION for a JAR or WAR deployment configured through that variable. If you supply your own JVM, image, or buildpack, make sure it installs or bundles a vendor-fixed runtime before you rebuild and redeploy. Java on Scalingo · Deploying JAR and WAR archives
  2. Redeploy with a fresh build. With Scalingo’s standard JVM buildpack, trigger a new build and deploy the resulting release. The default and affected major-version selectors resolve to the updated JDK during the build. A restart starts the same release with its existing JVM. Buildpack version resolution

Verify the fix

After the rollout succeeds, run this command for each application. Replace my-app and osc-fr1 with your application name and region. The command reports the Java version in a one-off container from the deployed release. Scalingo one-off containers

scalingo --region osc-fr1 --app my-app run "java -version"

Expected result - For the standard Azul Zulu buildpack, the output reports the fixed version for your Java line: 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1, or a later build confirmed to include the fix by Azul. If your output still shows an affected build, check for an exact version pin, rebuild, and verify again.

If the version still does not match your vendor’s fixed build, contact Scalingo Support with your application name, region, and the output of java -version.

Temporary JVM workaround

For Java applications you deploy on Scalingo, check your JVM vendor’s guidance if you cannot deploy a fixed build immediately. On affected HotSpot builds that support the option, Red Hat recommends adding -XX:-UseBASE64Intrinsics to the JVM startup options. Restart every affected Java process with the option, confirm it took effect, and check that the application starts and works as expected. Remove the option after deploying and verifying a fixed build. Red Hat mitigation guidance

Scalingo for OpenSearch

When the security update becomes available, open the database dashboard for each Scalingo for OpenSearch add-on and start the upgrade. Scalingo will update this bulletin with the patched add-on revision once it is available. After the upgrade, verify that your add-on shows that revision in the database dashboard. If the upgrade fails, contact Scalingo Support with your add-on ID and region. Database dashboard

Product Impacts

Scalingo PaaS

Applications running an affected JVM need a fresh build with a fixed JDK.

Scalingo DBaaS Add-ons

  • Scalingo for OpenSearch is affected by CVE-2026-114938. A non-Java service authenticates customer requests before they reach OpenSearch. This limits exposure and allows us to target Tuesday, November 24, 2026, for the fix. Scalingo for OpenSearch
  • Scalingo for Elasticsearch uses OpenJDK 11, which is outside the affected release lines for CVE-2026-114938. No customer action is required for this add-on. Scalingo for Elasticsearch · OpenJDK advisory

Other Scalingo Add-ons and Services

There is no impact on other Scalingo add-ons and services.

Contact

If you have any questions or concerns regarding this bulletin, please contact Scalingo Support using the chat in your dashboard.

Timeline

Date Milestone
2026-11-17 OpenJDK and Java vendors publish security updates.
2026-11-18 10:40 Scalingo merges the updated JDK defaults into its JVM buildpack repository.

Changelog

  • 2026-11-18 - Initial publication.

Suggest edits

SSB-2026-008 - Java4Shell vulnerability in OpenJDK (CVE-2026-114938)

©2026 Scalingo