r/java • u/philipwhiuk • 23h ago
Java RCE CVE-2026-114938
https://www.aikido.dev/blog/java-17-rce-vulnerability-cve-2026-11493877
u/SleeperAwakened 23h ago edited 21h ago
I really hope that this is a storm in a glass and an attempt for a few minutes of fame.
I really hope that it is no RCE flaw in Base64 which is used everywhere in HTTP payload like cookies, JWT etc.
The latter would make PHP and eMudhra feel like a gentle breeze in comparison. Fingers crossed.
UPDATE
Frell, seems indeed to be in Base64... Damn This is bad, we have some patching to do ASAP!
UPDATE2
All Java users should update immediately.
You can also mitigate Java4Shell by starting OpenJDK with either:
-XX:-UseBASE64Intrinsics to disable hardware-accelerated Base64 encoding and decoding, or
-XX:UseAVX=2 to disable AVX-512. Apply this flag only on x86-64 hosts. OpenJDK on ARM doesn't recognize it and will fail to start.
10
16
u/keenOnReturns 21h ago
https://github.com/corretto/corretto-25/commit/25bb7d35dcc1a7092eca2ba08124c85b3deec8a2
Corretto (Amazon’s Java) already patched BTW
8
2
u/stargazing_penguin 21h ago
Update to what? As far as I can tell this effects the latest version of the JRE
4
u/SleeperAwakened 21h ago
Latest OpenJDK of your preference. I hope for faster releases than last month.
1
159
u/FriendOfMandela 21h ago
Java 17, 21, 25 and 27
Thank god we're still on Java 8
/s
19
u/Jotakin 14h ago
Thank god our server hardware is 13 years old and thus cannot have AVX-512
/s
2
u/AloneInExile 9h ago
You're lucky!
Our server hardware is so old it doesn't even have hyperthreading!6
5
u/rahvan 7h ago
2
u/ChanceFly9724 2h ago
From what I've read thus far its a specific Oracle Perf LTS build (Oracle's Java 8 Enterprise Performance Pack) of Java 8 with the CVE-2026-114938 issue and doesn't apply to other OpenJDK 8 versions.
Did I miss something?
2
u/bigkahuna1uk 10h ago
I was wondering if there would even be a fix by Oracle if Java 8 was affected.
1
u/koflerdavid 3h ago
There will be. That's what LTS is about: no new features, no performance optimizations, just certain selected fixes and security patches.
34
u/joschi83 22h ago
From https://calif.io/java4shell/
Because the vulnerable code is hardware-specific, Java4Shell also requires an x86-64 processor with AVX-512 VBMI support. ARM64 CPUs are not affected.
21
u/witness_smile 22h ago
Alright so we’ve had PHP, then NodeJS, and this week Java. Wonder what C#’s CVE will be next week
14
u/Kjufka 22h ago
c# is just a language - it's runtime already had multiple RCEs this year.
Notably that Brotli RCE used in Node2Shell - C#/dotnet was also affected and it had score of 9.2, but it seems nobody cares about it enough to make a big deal out of it? maybe a 9/10 CVE is just a normal Tuesday for C# guys
4
u/SleeperAwakened 22h ago
3 billion devices was ages ago. Who knows the number now. eMudhra was bad enough with all the embedded devices. I really hope this turns out to be nothing.
1
u/koflerdavid 3h ago
People should have seen this coming and started planning ahead back when Log4shell was found. This time the fix is quite simple: patch the JVM as soon as possible. Cthulhu help you if your operations cannot do even that because this is not the only juicy CVE that has been found all those years. Differently from Log4shell and eMudhra however, edge deployments such as set-top boxes should be safe since AVX512 is only supported on quite recent high performance CPUs.
-1
u/AloneInExile 9h ago
Java cannot be run on more than 3 billion device, each time a new device is added an old one is removed.
By the latest estimates, > 15billions i the right number.
18
13
u/got_milk4 21h ago
There's a detection script available here.
Also note that the limitations section on the source's website suggests request buffering may provide some form of mitigation.
For what it's worth, the detection script against my Java 21 workloads on EKS returns 'not impacted' on all nodes, none of our instances are on types that support AVX-512 as far as I can tell.
20
u/lurker_in_spirit 20h ago
Claude, submit a PTO request for the next 5 work days. Do not take "no" for an answer.
14
u/EvaristeGalois11 21h ago
Hopefully temurin will patch it quickly too, they are not very speedy with the release process
3
5
u/keenOnReturns 21h ago
that’s one of the reasons why you go with other distributions with more strict SLAs
11
u/EvaristeGalois11 21h ago
But I like how the name sounds :(
1
u/keenOnReturns 21h ago
Well temurin is the most community driven, but that also means it probably receives the least funding compared to other distributions by major enterprises. It also doesn’t help they support a wider range of platforms compared to most.
If you’re simply using Java for development or a hobby project, they’re fine. But any public service, you probably need automated updates with a better supported distribution.
10
2
u/6000rpms 19h ago
Does anyone know the market share for the various Java distributions? I feel like most open source projects use Temurin, and given that most software is open source, this feels like an 0day for the majority of Java apps.
1
u/keenOnReturns 18h ago
Hard to track, given it’s simply binaries and at best you’d have to go by download numbers (which most distributions don’t publish). You could go by docker image pulls as a proxy (although it’s not truly indicative of what’s actually running). Yeah temurin is kinda the default, simply because it’s the most community driven with the least affiliations.
2
u/Key-Teach420 15h ago
I am currently on temurin, any suggestions on what should I do?
1
u/DanLynch 7h ago
It seems like using -XX:-UseBASE64Intrinsics avoids the bug, but it may slow down your application.
0
u/CodeDead-gh 13h ago edited 2h ago
Switch to Coretto or Oracle OpenJDK if permitted, patches there are already available.
If not permitted to use a patched jvm due to licensing or whatever: pull services offline and wait for a patch or set the appropriate jvm flags to mitigate the issue
2
2
2
u/HighHood 3h ago
There is a quick fix
https://github.com/theori-io/java4shell-runtime-patch-CVE-2026-114938
1
u/neopointer 12h ago
Does anyone else have the same understanding as me that the vulnerability does not apply if you're using graalvm's native image compilation?
2
u/CodeDead-gh 12h ago edited 10h ago
Oracle GraalVM confirmed affected.
Source: https://calif.io/java4shell
1
0
u/Rockytriton 15h ago
wake me up when amazon corretto image gets updated
9
3
0
-7
u/brunocborges 13h ago
Another case for folks to consider brewlet.sh so platform teams can roll out security patches quickly.
3
20h ago edited 19h ago
[removed] — view removed comment
5
4
u/pron98 18h ago
Just a reminder that the Oracle JDK gives you free LTS updates for 3 years, so Oracle JDK 25 updates are still free. It's only after 3 years that you need to buy a subscription to download LTS updates (so to use the update for JDK 21 in production you need a subscription).
5
u/keenOnReturns 18h ago
why bother with Oracle though when there are free options?
3
u/pron98 16h ago
Oracle JDK is also a free option. Don't have to choose it, but just so you know.
1
u/keenOnReturns 13h ago
is it free in production? also, u say “free” with the big asterisk of 3 years. Meanwhile you can use openjdk 8-21 until 2030+ with basically any provider.
1
u/pron98 8h ago
Yes, it's free in production. And BTW, it's also OpenJDK (OpenJDK JDK is the name of Oracle's source implementation of Java; Corretto, Oracle JDK, and others are built from it).
0
u/keenOnReturns 3h ago
Oracle JDK ≠ OpenJDK. Oracle does do openjdk builds (the free stuff you mentioned might simply be that), but the paid product is actually their proprietary, closed source implementation of the JDK. In reality, they probably share 90%+ identical code, but licensing and legal-wise, they are not the same thing.
3
u/pron98 2h ago edited 1h ago
That is inaccurate on multiple fronts.
OpenJDK is a group of projects, but the OpenJDK JDK project, which is developed by Oracle (with contributions from others), isn't a distribution at all. It's a source project, not a deliverable. The OpenJDK JDK is the source from which Oracle JDK and Correttor and others are built. I.e. it's true that Oracle JDK ≠ OpenJDK JDK, but also Corretto ≠ OpenJDK JDK in a similar way. There is simply no distribution by the OpenJDK project. The distributions are built in slightly different ways by different distribution vendors, but none of them is the OpenJDK JDK, which is only about the sources.
While the Oracle JDK - which, like Corretto, is built from the OpenJDK JDK sources - is free, it does have a different licence from the OpenJDK JDK source licence (GPLv2 + CPE), because Oracle owns OpenJDK, and so we can distribute builds under a different licence. But we do also offer builds with the GPLv2 + CPE licence.
The Oracle JDK builds are not really built from our proprietary sources. The OpenJDK JDK is the one implementation of Java developed by Oracle (with contributions from others). No more is added to the builds than what other distros do (Corretto also adds some code that isn't in the OpenJDK JDK), and especially their update releases can contain different backports. The backported patches, however, in the Oracle JDK, are not open source.
This works the same as Linux. There is one official Linux kernel project, which corresponds to the OpenJDK JDK, but there is no Linux distribution by that project. Every distribution takes the Linux kernel sources and builds it (with its own additions/modifications) - that corresponds to Oracle JDK/Corretto/etc..
10
u/best_of_badgers 23h ago
My understanding is that this CVE was not included in the November 2026 CPU. It's a separate TBD patch. Is that not true?