News for hackers. Stuff that matters.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ievans on Tuesday November 17, 2026 @04:23PM (#50538391)
Super impressive work by Calif as usual.

The exploit conditions are very specific but there are still going to be a lot of hosts impacted. We at Semgrep published some free detection scripts here: https://github.com/semgrep/detection-scripts/tree/main/CVE-2...

They look for these five conditions:

  * HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].
  * x86-64 JVM on an x86-64 host.
  * Version 17.0.6 or later, not at or above a version listed in FIXED_IN, and no newer than the newest releases checked (see below). Newer versions are [?]: they may carry the fix.
  * The JVM reports avx512_vbmi and avx512bw, and UseAVX >= 3.
  * Base64 intrinsics are on and C2/JVMCI can compile. These turn it off: -XX:-UseBASE64Intrinsics, -XX:DisableIntrinsic=_base64_decodeBlock, -Xint, -XX:TieredStopAtLevel below 4.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by cjbprime on Tuesday November 17, 2026 @05:36PM (#50539263)
Wouldn't it be prudent for someone to patch even if they aren't running their code on an AVX512 system right this moment? They could be running on one.. next moment.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Banditoz on Tuesday November 17, 2026 @05:45PM (#50539343)
Sure, but I think it brings it down from "patch immediately" severity, to just "bump the JDK with next service deploy" severity.

Or, do running machines often have their CPU changed from under them without much notice?

Re:Java4Shell: RCE in OpenJDK when processing Base64 by stackskipton on Tuesday November 17, 2026 @05:55PM (#50539423)
Depends on the company and deployment method. As Ops person, I generally don't think much about rolling out different Kubernetes Nodes and what SKU I select. So yes, you could be running on one node type today and tomorrow I upgrade the nodes under you.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by xmodem on Tuesday November 17, 2026 @06:42PM (#50539846)
We’re using a second-tier cloud provider’s managed Kubernetes offering, and in investigating our level of exposure to this, I just learned that there is variance within a node pool on whether AVX-512 is available.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by jamesfinlayson on Tuesday November 17, 2026 @11:47PM (#50541993)
This - I remember taking a suggestion to cat cpuinfo as part of container start in AWS and you do get a bit of variety as you'd expect (five year old processors last time I checked as well).
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Sohcahtoa82 on Tuesday November 17, 2026 @06:39PM (#50539816)
> Or, do running machines often have their CPU changed from under them without much notice?

I dunno about other cloud providers, but I know AWS can move your EC2 VM from one system to another transparently. There is a server ID you can get from the metadata, but unless you're checking it frequently, you can be moved without ever being aware.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by PhilipRoman on Tuesday November 17, 2026 @07:11PM (#50540131)
Question is if they expose it to the guest. Many (most?) cloud platforms will make the guest see the lowest common denominator, specifically to avoid angry customers when their working setup suddenly breaks.

In the case of transparent migration, I think it's basically a must. No JIT (or even libc probably) is going to support CPU features changing at runtime.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by johnbellone on Tuesday November 17, 2026 @08:02PM (#50540529)
You’ll need to restart the guest.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by acdha on Tuesday November 17, 2026 @10:16PM (#50541422)
Not for a routine migration, but they typically keep it inside the same processor family for this reason.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Sohcahtoa82 on Wednesday November 18, 2026 @02:00AM (#50542789)
Not true.

AWS migrates live instances to new CPUs without needing to stop or reboot the guest.

When a migration is needed, the hypervisor begins copying blocks of memory to the new system, keeping track of what blocks are written inside the guest during the migration. Once enough has been copied, it hibernates the guest, copies the remaining memory, then wakes it in the new system. On a system that isn't writing to large swaths of memory, it can take only a few milliseconds. To the guest, it might appear that the CPU froze for a tiny bit of time, which could easily just look like a neighbor got noisy.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by mike_hearn on Wednesday November 18, 2026 @03:10AM (#50543278)
Yes, but that's irrelevant here because the CPUID report won't change across live migrations.

Consider what would happen if you were live migrated from a machine with AVX512 to one without. Your app would suddenly start crashing with SIGILL for no apparent reason. So, live migrations always preserve the apparent CPU feature set. If you started on a machine without AVX512 then until the VM is rebooted you will remain on such a (virtual) machine.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by tecleandor on Wednesday November 18, 2026 @06:14AM (#50544852)
But why would you live migrate between instances with a different instruction set? You'd need to emulate the missing instruction sets then...
Re:Java4Shell: RCE in OpenJDK when processing Base64 by bonsai_spool on Tuesday November 17, 2026 @05:36PM (#50539270)
This looks like Claudese - may be kind to write such things yourself if you intend for humans to read them. (For example, “ HotSpot VM: any OpenJDK build, Oracle JDK, or GraalVM JDK. Only HotSpot generates the stub. OpenJ9 and GCJ are OK. Azul Prime (Zing), which replaces C2 with its own JIT, and any VM name not recognized as HotSpot are [?], never [!].” — I tried parsing at least five times before realizing you’re asking me to decipher LLM talk)
Re:Java4Shell: RCE in OpenJDK when processing Base64 by Yokolos on Tuesday November 17, 2026 @05:48PM (#50539368)
I still don't understand what's meant with Azul. Is it affected or not? What is it never?
Re:Java4Shell: RCE in OpenJDK when processing Base64 by kaboberg on Tuesday November 17, 2026 @06:45PM (#50539883)
Azul Core definitely is - it uses upstream HotSpot.

Azul Platform Prime (formerly Zing) may or may not be depending on whether they touched the base64 intrinsic. Since it is closed-source there is no way to verify via code, which is how our research team investigates ecosystem events like this.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by pjmlp on Wednesday November 18, 2026 @03:44AM (#50543604)
I understood it on first read, anyone that is comfortable with Java ecosystem easily understands the differences between those JVM implementations.

Here are three more, PTC, Aicas, and ART (even if it runs DEX instead, and only the core language is supported).

Re:Java4Shell: RCE in OpenJDK when processing Base64 by stevenhuang on Wednesday November 18, 2026 @05:21AM (#50544398)
What's with this weird tendency to think everything you don't immediately understand is LLM? It's okay to not understand things. Have you worked with Java at all? Why do you expect to make sense of those technologies if not?

I've done Android development and there's nothing wrong with the way it's phrased. All of that is high signal information.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by bonsai_spool on Wednesday November 18, 2026 @06:13AM (#50544836)
This was written by Claude. It’s not a matter of comprehension at all but of odd diction that is charismatic of LLMs.

Thanks for the middlebrow dismissal

Re:Java4Shell: RCE in OpenJDK when processing Base64 by PantaloonFlames on Wednesday November 18, 2026 @10:46AM (#50547737)
It’s a phenomenon that is becoming more often recognized. The words string together but they’re constructed in a way that makes it either highly burdensome to parse or inconsistent. Characterized by Unrelated thoughts strung together; the unwritten limits of parenthetical count exceeded; non-specific referent pronouns; other subtle pitfalls. This is not a fault of the human reader.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by bikezen on Tuesday November 17, 2026 @05:40PM (#50539305)
The write-up itself matches your version assumption, however it also says:

> According to Oracle, the following Oracle Java SE versions are vulnerable: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3. We thank Oracle for providing this information ahead of publication time.

So according to Oracle at least, JRE8 versions are affected as well.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by xur17 on Tuesday November 17, 2026 @05:47PM (#50539362)
25.0.5.0.3 is the latest on the 25 version [0]. Does that mean no patch is available?

[0] https://www.oracle.com/java/technologies/javase/jdk25-archiv...

Re:Java4Shell: RCE in OpenJDK when processing Base64 by rhdunn on Tuesday November 17, 2026 @06:33PM (#50539756)
That's the archive page for older downloads. The main download page [1] reports the latest version as 25.0.5.1.

[1] https://www.oracle.com/java/technologies/downloads/#java25

Re:Java4Shell: RCE in OpenJDK when processing Base64 by K0IN on Tuesday November 17, 2026 @07:07PM (#50540088)
Ofc they needed 5 version numbers.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by nullpoint420 on Tuesday November 17, 2026 @10:55PM (#50541676)
Wow, yeah. Why do they need 5 version numbers!?
Re:Java4Shell: RCE in OpenJDK when processing Base64 by looperhacks on Wednesday November 18, 2026 @12:41AM (#50542298)
It's a bit of a mess. The first four are for the jvm, shared across all implementations: $FEATURE.$INTERIM.$UPDATE.$PATCH

$FEATURE: increased every six months when new features are released (or removed) $INTERIM: currently always 0, reserved for future use $UPDATE: non-feature releases like bug, security or regression fixes. Releases one month after the feature version; then every three months $PATCH: important updates out of schedule

Specific implementations may introduce a fifth component for updates that do not come from the shared implementation but are distribution-specific (think Oracle fixing a bug that only happens in Oracle distributions)

(Then there's more, like +2 build numbers, and older versions have a slightly different format)

Re:Java4Shell: RCE in OpenJDK when processing Base64 by testtestmetest on Tuesday November 17, 2026 @07:38PM (#50540335)
Calif is an OpenAI funded shop..
Re:Java4Shell: RCE in OpenJDK when processing Base64 by thephyber on Tuesday November 17, 2026 @08:01PM (#50540521)
Oracle owns Java and Oracle is "OpenAI funded" in the sense that Oracle's data center buildouts are being done using OpenAI as a consumer.

The circular financing continues!

But seriously, the funding here doesn't matter any more than Project Zero's funding comes from Google. Big companies are trying to improve security for the common software substrates of our industries / governments.

Re:Java4Shell: RCE in OpenJDK when processing Base64 by red-iron-pine on Wednesday November 18, 2026 @10:29AM (#50547509)
> Big companies are trying to improve security for the common software substrates of our industries / governments.

"improve security" in the same way that my dad used to beat us

Re:Java4Shell: RCE in OpenJDK when processing Base64 by apolo64 on Wednesday November 18, 2026 @10:37AM (#50547614)
Security by obscurity has never been a good idea, especially in the tech industry and even less so since the advent of LLMs
Re:Java4Shell: RCE in OpenJDK when processing Base64 by milkshakes on Tuesday November 17, 2026 @08:03PM (#50540544)
and?
Re:Java4Shell: RCE in OpenJDK when processing Base64 by sgammon on Tuesday November 17, 2026 @11:46PM (#50541986)
Native Image is also unaffected without `-march=native` which is not a default.
Re:Java4Shell: RCE in OpenJDK when processing Base64 by yburkov on Wednesday November 18, 2026 @08:07AM (#50545869)
one note: it means -XX:-UseBASE64Intrinsics OR XX:DisableIntrinsic=_base64_decodeBlock OR -Xint OR -XX:TieredStopAtLevel below 4 (-XX:TieredStopAtLevel=3 and so on)
Re:Java4Shell: RCE in OpenJDK when processing Base64 by ktm5j on Wednesday November 18, 2026 @10:19AM (#50547373)
They mention GraalVM being affected, but it seems like it isn't when I run their PoC:

  kmiles@dora tmp.wdOJ2BRVwa % java Base64Trigger 
  runtime=21.0.5+9-LTS-jvmci-23.1-b48
  vm=Java HotSpot(TM) 64-Bit Server VM
  rejected=true changed=0 first=-1 last=-1
  NOT REPRODUCED