Base64 turns binary data into plain text. Java applications decode it everywhere: login headers (Authorization: Basic), tokens such as JWT, cookies, file uploads, messages between services.
To go faster, Java compiles hot code into processor instructions while the application runs. On recent processors it uses a special routine that decodes 64 characters at once. That routine miscalculates the output size when the input ends with padding (=). It then writes 64 bytes past the end of its buffer, over whatever object sits next to it in memory.
The bytes written are mostly fixed, but an attacker can repeat the request and shape the memory around it. That is how the researchers moved from a crash to reading memory, then to running code.
Two details matter for defenders. The routine only kicks in after the decoder has been used many times, so a busy production server is more exposed than an idle one. And the attacker needs no account if the application decodes the value before checking the login, which is exactly what Basic authentication does.