What the advisory says
CVE-2026-114938 is a memory corruption issue in some Java virtual machine environments. Under specific CPU and runtime conditions, attacker-controlled Base64 data can reach the affected code. CERT-EU reports that this can cause a denial of service and, in some cases, remote code execution.
Exposure depends on the processor, runtime build, active feature and application data flow. Do not assume that every Java system is exposed or that a system is safe because it is not listed in a simple software inventory. Use the vendor advisory to assess each runtime.
Look beyond the server package list
List Java installations on servers, developer systems, build runners, container images and appliances. Check products that bundle their own runtime. Ask application owners and vendors which Java build their product uses and how they deliver security updates.
Prioritise internet-facing services and systems that process data from untrusted users. Include older images that remain available in a registry. An image can remain vulnerable even when the host has a newer Java package.
Patch, restart and record the result
Install the fixed build that applies to the distribution you use. Oracle, OpenJDK distributors and application vendors can publish fixes on different schedules. Follow the relevant provider’s instructions. Restart every affected Java virtual machine so that it loads the updated runtime.
Record the system, application, runtime vendor, build, update date and restart status. Check application health after the restart. If a system cannot be updated at once, ask the vendor for a supported mitigation and a dated patch plan.
Build a better software inventory
Treat bundled runtimes as part of the software asset, not as an exception. Add ownership and update responsibility to the inventory. A server security assessment can help review exposed services and patch management across the systems in scope.
