- cross-posted to:
- [email protected]
- cybersecurity
- cross-posted to:
- [email protected]
- cybersecurity
So, they went straight to public disclosure?
Recommendations
OpenJDK released a security advisory and Oracle released a patch at 1:00pm PT on Nov 17, 2026.
All Java users should update immediately.
You can also mitigate Java4Shell by starting OpenJDK with either:
-XX:-UseBASE64Intrinsicsto disable hardware-accelerated Base64 encoding and decoding, or-XX:UseAVX=2to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn’t recognize it and will fail to start.OK. I’ve got jenkins runing in certain places and OpenJDK installed. The fuck am I meant to do? How can I disable it system wide?
The best solution is to install the patched JDK once it’s available for your OS and JDK version. At least Temurin is taking their sweet time with it.
Setting JVM arguments for Jenkins depends on how it’s installed. For example, if it’s running as a systemd service, just add or modify:
[Service] Environment="JAVA_OPTS=-XX:-UseBASE64Intrinsics"There’s also
JAVA_TOOL_OPTIONS, which you can set globally, but I personally never use it.Unless you’re exposing Jenkins publicly, I wouldn’t worry too much about it. My understanding is that exploiting the vulnerability requires crafting a pretty targeted attack and I haven’t seen any reports of this being exploited at scale, even against publicly exposed services.
After we disclosed PHP2Shell, we realized many people didn’t know what PHP was. So we decided to go after something a little more familiar: Java.
haha






