A Fortra expert on Java4Shell and Oracle’s latest security update

Get ready to patch all the things as the Java4Shell vulnerability which was found is breaking alongside today’s Oracle security update to fix this. Having said that Tyler Reguly, Associate Director of Security R&D at Fortra had this commentary:

When Oracle moved to monthly patch drops in May of this year, there were only 35 patches included in the drop. From the start of the monthly patch drops, Oracle has dropped 5,294 patches including the November drop. That works out to ~756 patches per month. For the entire year, Oracle has released 6112 patches. Across the four Critical Patch Updates (CPUs) in 2025, Oracle dropped only 1379 patches. That means that we’ve seen a 4.4x increase in the number of patches released by Oracle in 2026 and we still have December to go.

Today, everyone is going to be talking about Java4Shell, which affects OpenJDK’s Base64 decoder and is part of the Oracle Critical Security Patch Update (CSPU) because Java SE is also impacted. Calif Research has published an excellent write-up on this vulnerability, providing impacted products, demo videos, and an explanation of the vulnerability. The one thing that I found missing was a CVSS vector. Oracle has this vulnerability listed as 8.1, while Calif calls it a 9.2. That’s a pretty big separation that changes the issue from High to Critical. However, Oracle uses CVSS 3.1, while Calif is using CVSS 4.0. Having the vector information would allow for a better comparison of those values to see if the two scored it differently or if the disparity is simply caused by differences in the versions of the scoring standard.

When you consider how popular Java is and pair that with the Calif video that shows them easily exploiting multiple pieces of off the shelf software that incorporate Java, you have to wonder how big this has the potential to be. It’s still early in the process and there’s a lot to digest, but teams will likely want to start their internal threat assessments sooner rather than later. I feel bad for security teams on the east coast of North America who were just about to start wrapping up their day when this dropped and in Europe because they were likely settling in to relax after dinner. I know there’s never a good time to drop a vulnerability like this, but I selfishly wish it was earlier in my day.

Leave a Reply