Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938)
by marginalia_nu on Tuesday November 17, 2026 @05:47PM
(#50539363)
Why'd you patch the commandline of JVMs that aren't vulnerable though?
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938)
by xboxnolifes on Tuesday November 17, 2026 @06:27PM
(#50539684)
So you don't need to check every host individually, you just patch all of them for now.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938)
by eru on Tuesday November 17, 2026 @06:57PM
(#50540003)
Especially since that check might have further problems. The simpler you can make your code (and still solve the problem) the better.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938)
by marginalia_nu on Tuesday November 17, 2026 @07:06PM
(#50540084)
I don't know if I'd count paving over the reality of what you're running with an abstraction layer as something simpler. If anything it demonstrably makes addressing issues like these harder.
Re:Pre-auth RCE flaw in Java 17 and later (CVE-2026-114938)
by articulatepang on Tuesday November 17, 2026 @08:01PM
(#50540522)
I think you're right, but many people are running systems at large scale, with lots of hosts and all kinds of abstraction layers and stuff. Now this exploit shows up. What are they to do? It's just a practical thing they can do right now.
First we must stop the bleeding. After that, yes, it's worth figuring out if they should change how things are set up.
I've been in situations like this before. Sometimes the complications and abstractions were my fault, sometimes I inherited them. Either way, as responsible owners of the overall system or business, we've gotta be able to respond fast to issues.
Until, presumably, there’s fixes and you can test, update etc.