Critical Java flaw in OpenJDK could allow remote code execution, with patching expected to be slow
Because many operating systems, containers and applications ship their own Java runtime, fixed releases will reach systems unevenly and over a long period.

A critical flaw in OpenJDK, the codebase underlying nearly every Java distribution, allows remote code execution and in many cases needs no login. Calif Research, which named it Java4Shell, rates it 9.2 on CVSS 4.0, while vendor ratings from Oracle and Red Hat fall between 8 and 9.8. The bug sits in a hand-written assembly optimization for Base64 decoding that fails a bounds check, so an attacker supplying 64 characters followed by padding can overwrite adjacent memory. Exploitation requires an x86-64 CPU with AVX-512 and the VBMI extension, such as Intel Ice Lake or AMD Zen 4 server chips. Oracle has shipped fixed releases, but because many operating systems, containers and applications bundle their own Java runtime, patching will be spread out and slow.
Why it matters
The flaw sits in the codebase underlying nearly every Java distribution, so it reaches far beyond any single vendor's product. Oracle has already fixed the bug and issued updated versions, but many operating systems and individual programs carry their own copy of a Java executable, which means each copy must be updated separately. Exploitation is limited to x86-64 processors with AVX-512 and the VBMI extension, such as certain Intel and AMD server chips, which narrows the systems at risk but does not remove the wide exposure for those that match. For ordinary users and operators, the practical effect is that a fix exists but will take time to reach every place it is needed.
Matters or hype?
Does this story matter, or is it hype? Vote before you see what everyone else said.