Fuzzball v4.4.2 release notes
Fuzzball v4.4.2 is a security patch release. It mitigates the Java4Shell vulnerability (CVE-2026-114938) in Keycloak, the identity provider that Fuzzball deploys for Orchestrate and Federate, and moves the Kong ingress gateway to a release that fixes the NGINX2Root HTTP/2 vulnerabilities.
Fixes
Security
- Fixed an issue where Keycloak ran on an OpenJDK release affected by
Java4Shell (CVE-2026-114938), a heap overflow in the JVM's built-in Base64
decoder that unauthenticated requests to Keycloak can reach. Only x86-64
hosts whose CPUs support AVX-512 VBMI are exposed: Intel Ice Lake or newer,
and AMD Zen 4 or newer. ARM64 hosts are not affected. Keycloak now starts
with
-XX:-UseBASE64Intrinsics, which turns off the affected code path. No Keycloak image with a fixed JDK is available yet, so this flag is the mitigation until one is.- Deployments managed by the Fuzzball operator, both Orchestrate and Federate, get the flag when you upgrade. The Keycloak pods restart once to pick it up.
- Docker Compose deployments get the flag from
fuzzball cluster docker-compose update, which sets it inJAVA_OPTS_APPEND. Adocker-compose.override.yamlthat replacesJAVA_OPTSkeeps the mitigation, but if your override also setsJAVA_OPTS_APPEND, add-XX:-UseBASE64Intrinsicsto it.
- Fixed an issue where the Kong ingress gateway that Fuzzball installs ran
Kong 3.6, which is affected by the NGINX2Root HTTP/2 vulnerabilities
(CVE-2026-123007 and CVE-2026-123633). Fuzzball now deploys the
docker.io/kong/kong:3.9.5gateway image, and the gateway pods restart once when you upgrade.- If you mirror Fuzzball's images to a private registry, add
docker.io/kong/kong:3.9.5to the mirror before you upgrade. - A deployment that uses its own ingress controller instead of the one Fuzzball installs is not changed. Update that controller separately.
- If you mirror Fuzzball's images to a private registry, add