Skip to main content

Security Advisories

This page covers security vulnerabilities that need more than a Mango upgrade: for example a flaw in the Java runtime, which Mango does not install outside of the Docker image. Each entry says who is affected, how to fix it, and what to do if you can't update straight away. The release notes list every security fix that ships in Mango itself.

CVE-2026-114938 (Java4Shell)​

PublishedNovember 17, 2026
SeverityCritical (CVSS 4.0 score 9.2)
ComponentJava runtime (OpenJDK and every distribution built from it)
Fixed inMango Docker images 5.7.9 and 5.6.16; Java 17.0.21.1, 21.0.13.1 and 25.0.5.1
Detailscalif.io/java4shell, CERT-EU advisory 2026-021

CVE-2026-114938 is a memory-corruption flaw in the hardware-accelerated Base64 decoder of the Java runtime. A crafted request can make it write past the end of a buffer, which an attacker can use to run code inside the Java process.

Who is affected​

A Mango installation is affected when both of these are true:

  • It runs on Java 17.0.6 to 17.0.21, 21.0.13 or earlier, or 25.0.5 or earlier, from any vendor (Azul Zulu, Eclipse Temurin, Amazon Corretto, Oracle and others). This includes every Mango Docker image published before 5.7.9 and 5.6.16.
  • The server has an x86-64 CPU with AVX-512 VBMI: Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids or Granite Rapids, or AMD EPYC and Ryzen Zen 4 or later.

ARM64 servers are not affected.

To check a Linux server's CPU, run:

grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'

The CPU is affected only if all four flags (avx512f, avx512bw, avx512vbmi and bmi2) are printed.

Fix​

  • Docker: Upgrade to the 5.7.9 or 5.6.16 image tag, or later. Both run Java 21.0.13.1. If you use a floating tag (latest, 5, 5.7 or 5.6), it now points to a fixed image, but your container keeps running the image it was created from until you pull the tag again and recreate the container, for example with docker compose pull && docker compose up -d. To check a running container, run docker exec <container> java -version.
  • All other installations: Mango runs on the Java installed on the server, so upgrading Mango doesn't change it. Update Java to 17.0.21.1, 21.0.13.1 or 25.0.5.1 or later, depending on your Java version, then restart Mango. Vendors also give their builds their own release numbers: for example, Azul Zulu 21.54 is Java 21.0.13.1, so java -version shows 21.0.13.1 together with Zulu21.54.

Workaround until you can update​

Start Java with the option -XX:-UseBASE64Intrinsics. It turns off the hardware-accelerated Base64 code that the attack needs, and Java uses its standard Base64 implementation instead. The option works on every CPU architecture, and you can remove it once Java is updated.

Pass the option in the JAVA_TOOL_OPTIONS environment variable, which Java reads whichever way Mango is started:

  • Docker: Add -e JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics to docker run, or set it under environment: in your Compose file, and then recreate the container.

  • Linux with systemd: Run sudo systemctl edit mango, add these lines, and then run sudo systemctl restart mango:

    [Service]
    Environment="JAVA_TOOL_OPTIONS=-XX:-UseBASE64Intrinsics"
  • Windows service: Add this line inside <service> in mango.xml in the Mango data directory, next to the other <env> entries, and then restart the Mango service:

    <env name="JAVA_TOOL_OPTIONS" value="-XX:-UseBASE64Intrinsics"/>

    Setting a system environment variable instead is not enough. A Windows service only sees the system variables that existed when the machine started, so Mango would keep running without the option until the next reboot.

To confirm that the option is in use, list the flags of the running Mango Java process with jcmd, which ships with the JDK. The output must include -XX:-UseBASE64Intrinsics.

  • Docker: docker exec <container> jcmd 1 VM.flags
  • Linux and Windows: run jcmd with no arguments to list the Java processes, then jcmd <pid> VM.flags with the process ID of Mango.

In Docker, docker logs <container> also shows Picked up JAVA_TOOL_OPTIONS: -XX:-UseBASE64Intrinsics when the container starts.