dot CMS

Is dotCMS affected by the Java4Shell vulnerability?

Is dotCMS affected by the Java4Shell vulnerability?
Freddy

Freddy Montes

VP of Product

Share this article on:

Partly. dotCMS Cloud is already protected and Cloud customers have nothing to do. If you run dotCMS 24.08.27 or later on your own servers, add one JVM option and restart. The vulnerability is CVE-2026-114938, known as Java4Shell.

Three weeks ago we wrote that PHP2Shell did not affect dotCMS because we run on Java, and that we were treating it as a drill for our own stack. This one is ours.

What happened

On November 17, 2026, researchers at Calif disclosed a memory corruption bug in the Java runtime itself. Java uses hand-tuned processor instructions to decode Base64 faster, and on some processors a malformed Base64 string makes that code write past the end of its buffer. The researchers report that this can lead to remote code execution without authentication. Other security teams who reproduced it say a crash of the Java process is the more likely result. No exploitation in the wild had been reported as of November 17.

Three conditions have to be true together:

  • Java version. Java 17.0.6 and later, 21, 25, and 27, before the builds released on November 17. Java 11 is not affected.

  • Processor. An x86-64 CPU with AVX-512 VBMI: recent Intel Xeon (Ice Lake and newer) and AMD Zen 4 and newer. ARM64 processors are not affected.

  • Input. The application decodes Base64 that an attacker controls. Almost every Java web application does this before login, in authentication headers and tokens. dotCMS does too.

The bug is in the runtime, not in dotCMS code, so no dotCMS setting or permission prevents it.

dotCMS Cloud: no action required

Every dotCMS Cloud environment is either not affected or already mitigated, whatever dotCMS version it runs.

Our AWS environments run on ARM64 processors, which do not have the vulnerable code. For environments on x86 processors, we added the JVM option below and restarted them within hours of the disclosure, the same day. We emailed Cloud customers on November 17 to confirm it.

Self-hosted dotCMS 24.08.27 and later: action required

Add this option to the JVM arguments on every dotCMS instance:

-XX:-UseBASE64Intrinsics

If you run the dotCMS Docker image, add it to CMS_JAVA_OPTS next to the settings you already have. For example, if you currently set -Xmx5G:

CMS_JAVA_OPTS: '-Xmx5G -XX:-UseBASE64Intrinsics'

Keep your own memory value; -Xmx5G is only an example.

Then restart each instance. The option has no effect until the JVM restarts. To confirm it is applied, run this against the dotCMS process and check that the output includes -XX:-UseBASE64Intrinsics:

jcmd <pid> VM.flags | grep BASE64

The option turns off the accelerated Base64 decoder, so Java uses its standard decoder instead. Nothing else changes. It is safe on any processor, so apply it even if you are not sure which CPU your servers have.

What comes next

The JVM option is a mitigation. The fix is a patched Java runtime, and we will ship dotCMS releases built on one as soon as the patched builds are available to us. We will update this post with the version numbers when they are out. The option can stay in place after you upgrade.

If you have questions about your deployment, open a support ticket or write to security@dotcms.com. Our published advisories are on the known security issues page.

Next: ask Will to confirm items 1 and 2; both are one-line answers.

Sources:

Recommended Reading
  • Managing Users, Roles and Tools Just Got Easier
    9 Nov 26
    Product

    Managing Users, Roles and Tools Just Got Easier

    Manage access in dotCMS with new dedicated Roles, Tools and Users screens. Create roles, grant tool groups, customize admin navigation, and manage users in a searchable table, all under Settings with a modern, unified admin experience.Manage access in dotCMS with new dedicated Roles, Tools and Users screens. Create roles, grant tool groups, customize admin navigation, and manage users in a searchable table, all under Settings with a modern, unified admin experience.

    Marc

    Marc Boutillette

    Outbound Product Manager

  • The Timeline Was Written by the Attacker
    27 Oct 26
    Product

    The Timeline Was Written by the Attacker

    A state-linked supply chain attack, AI-built exploits active in the wild today, and why dotCMS is doubling down on open source.

    Stephen

    Stephen Freudenthaler

    Director of Engineering

  • Content Modeling Best Practices: How to Structure Content for Reuse Across Pages, Sites, and AI
    19 Aug 26
    Product

    Content Modeling Best Practices: How to Structure Content for Reuse Across Pages, Sites, and AI

    Learn content modeling best practices to structure entity-centric, reusable content for pages, multi-site and multi-channel delivery, and AI search.

    Marc

    Marc Boutillette

    Outbound Product Manager

  • Driving Content Innovation: Our 2026 Roadmap
    3 Mar 26
    Product

    Driving Content Innovation: Our 2026 Roadmap

    Join VP of Product Freddy Montes for a walk through of the exciting things dotCMS is working on in 2026

    Freddy

    Freddy Montes

    VP of Product

Explore dotCMS for your organization

image

dotCMS Named a Major Player

In the IDC MarketScape: Worldwide AI-Enabled Headless CMS 2025 Vendor Assessment

image

Explore an interactive tour

See how dotCMS empowers technical and content teams at compliance-led organizations.

image

Built for Compliance. Certified for AI.

dotCMS is ISO 27001 and ISO 42001 certified, pairing independently verified information security with governed, accountable AI.