Skip to main content
All posts

Kviklet 0.10.1 Release Notes

Kviklet 0.10.1 is out! This is a security release. We recommend that everyone upgrades.

A critical vulnerability in the Java runtime was published yesterday: CVE-2026-114938, also known as "Java4Shell". It is a memory-corruption bug in the JVM's hardware-accelerated Base64 decoder. Kviklet decodes Base64 from requests before login (for example the session cookie), so the vulnerable code can be reached without credentials.

Who is affected​

Kviklet instances running on x86-64 CPUs with AVX-512 VBMI (Intel Xeon Ice Lake and newer, AMD Zen 4 and newer). ARM hosts are not affected. We are not aware of a working exploit against Kviklet, but we treat this as critical.

What this release does​

  • Kviklet now starts the JVM with the hardware-accelerated Base64 decoder switched off, which removes the vulnerable code path. The only effect is slightly slower Base64, which you will not notice.
  • The bundled Java runtime is updated from 21.0.9 to 21.0.13 and now follows the latest JDK 21 patch release with every Kviklet release.

A patched JDK is not available yet. We will ship it in a follow-up release once it is.

If you cannot upgrade right away​

Set this environment variable on your existing Kviklet container and restart it:

JAVA_OPTS=-XX:-UseBASE64Intrinsics

If you already set JAVA_OPTS, add the flag to the existing value.

About the nginx HTTP/2 vulnerabilities​

Kviklet is not affected by CVE-2026-123633 and CVE-2026-123007. Both require HTTP/2 to be enabled in nginx, and the nginx inside the Kviklet image does not enable it. We will still update nginx as soon as the fixed base image is available.

There are no other changes in this release. You can find it on Github. If you have questions about this fix, feel free to open an issue on Github or reach out to me directly.