lazarus

A runtime for Minecraft Forge 1.8.9 on modern Java, with optional LWJGL 3 and security patches.

Security

Running a 2015 game on a 2026 JVM changes its attack surface in both directions. Lazarus closes the known holes it can reach; this page lists them and what it does about each.

Log4Shell (CVE-2021-44228, CVE-2021-45046, CVE-2021-45105)

Minecraft 1.8.9 ships Log4j 2.0-beta9, the first version affected. Log4j expands ${...} lookups inside logged messages, so any text that reaches the log (chat from a server, a player name, a sign) is evaluated. That enabled remote code execution through ${jndi:ldap://...} and a recursive-lookup crash.

Lazarus patches Log4j as it loads:

Every CI run logs a JNDI payload aimed at a local listener plus a ${sys:...} lookup, and fails if either is expanded or anything connects. On a stock Forge 1.8.9 launch the ${sys:...} lookup does expand.

Java4Shell (CVE-2026-114938)

Disclosed 2026-11-17. On x86-64 CPUs with AVX-512 VBMI (Intel Ice Lake and later, AMD Zen 4 and later), HotSpot’s Base64 decode intrinsic in Java 17, 21, 25 and 27 writes past its buffer for crafted input, which can lead to remote code execution in any code that decodes attacker-controlled Base64 with java.util.Base64. Java 8, the game’s original runtime, is not affected, so moving the game to modern Java would add this exposure.

Lazarus always runs with -XX:-UseBASE64Intrinsics, the advised stopgap:

The flag only switches off a fast path; decoding stays correct. It is safe on JVMs without AVX-512 and on JDKs that already contain the fix. Still update to a fixed JDK when your distribution ships one (for example Corretto 25.0.5.1.2, 21.0.13.1.2 or 17.0.21.1.2, or Oracle 25.0.5.1); the same release fixes nine other JDK CVEs.

Not affected

What Lazarus does not change

Report vulnerabilities privately; see SECURITY.md.