Repository navigation
CVE-2026-114938 (Java4Shell) in the Apollo 3.0.0 images - mitigation available now #5719
nobodyiam
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
The official Apollo 3.0.0 images ship a Java runtime affected by CVE-2026-114938 ("Java4Shell"), a heap out-of-bounds write in the HotSpot Base64 decoder on x86-64. We have reproduced the issue independently and confirmed the reach on a live Apollo 3.0.0 configservice.
A one-line mitigation is available today and fully closes this path. A rebuilt image with a fixed runtime will follow once the upstream Temurin container image is republished.
No remote code execution against Apollo has been demonstrated, and no in-the-wild exploitation was known as of 2026-11-18.
Affected versions
eclipse-temurin:17-jre-jammy)Mitigation (do this now)
Set this JVM flag on every Apollo service and restart:
Docker example:
Or in docker-compose, add it under
environmentfor each service. The flag disables the vulnerable intrinsic; we verified it as a clean control in our reproduction. The performance impact is negligible for Apollo, since Base64 is only used for small inputs such as auth headers.Verify the flag reached the JVM after restart:
It should show
UseBASE64Intrinsics = false.What does NOT fix it yet
Rebuilding the image today does not fix it. The fixed Temurin build 17.0.21.1+2 exists as a binary, but the
eclipse-temurin:17-jre-jammycontainer image has not been republished yet (last updated 2026-11-12), so a rebuild still pulls the vulnerable runtime. Do not rely on a rebuild until that image is updated.What is next
Credit
Thanks to Tony U (EZO Labs Security, @superbot-helper on GitHub) for reporting this to apollo-config@googlegroups.com.
All reactions