This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers

Last month, the details of PHP2Shell leaked before the embargo lifted, and PHP had to scramble its release out early. This week, the same research firm, Calif, had it happen again, this time with Java. Java4Shell (CVE-2026-114938) is a heap overflow in OpenJDK’s hardware-accelerated Base64 decoder, and on November 17, Calif said it was going public early because the vulnerability had leaked. Oracle and OpenJDK pushed fixes that afternoon, and Calif followed with its write-up.

Java normally runs virtual bytecode inside the Java virtual machine, but when a function gets called often enough, the HotSpot JIT compiler turns it into native code. For some common operations it goes a step further, and swaps in hand-tuned machine code which uses special CPU instructions. On x86-64 CPUs with AVX-512 instructions, Base64 decoding is one of those, chewing through 64 bytes at a time with a mask that decides which output bytes actually get written. When the last chunk of input is a short, malformed tail with “=” padding, the calculated output length underflows below zero, the mask ends up with every bit set, and the decoder writes 64 bytes where it should have written at most two. Java then correctly throws an exception for the bad input, but by then, 62 bytes past the end of the output buffer have already been overwritten.

The overwritten bytes are fixed; the attacker controls when and where the write happens, but not what is written. Calif turned that into a working exploit anyhow. The overflow overwrites the length field of a nearby array, which allows for overwriting more of the heap with chosen values, and then into a way to read heap memory back in a response, which may hold keys, tokens, and other secrets. From there, Calif escalated to code execution, grooming the heap remotely by carefully timing the pieces of the HTTP request. Calif is holding back the exploits for specific applications for now, and points out that every target needs its own custom setup.

Not every Java server is vulnerable. The bug needs OpenJDK 17.0.6 or newer, and an x86-64 processor with AVX-512 VBMI, which in practice means Intel Ice Lake or newer server chips, or AMD Zen 4 or newer; ARM servers are safe. The decoder also has to be JIT compiled first, which Upwind found took about 10,000 decodes, so a busy server qualifies and an idle one may not. Unfortunately, Base64 shows up everywhere attacker input arrives. i’IUpwind found that the standard HTTP Basic authentication handling in Spring Security, Tomcat, and Jetty, as well as Auth0’s java-jwt library, feed attacker-supplied data to the vulnerable decoder before checking any credentials. If you can’t update yet, starting Java with “-XX:-UseBASE64Intrinsics” disables the vulnerable code. Unlike Log4Shell, this is a bug in the Java runtime itself, not in a library, so dependency scanners won’t find it, and the fix means replacing the runtime everywhere it lives, including inside every container image.

Continue reading “This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers” →

We’re Hiring: Come Join Us!

You wake up in the morning, and check Hackaday over breakfast. Then it’s off to work or school, where you’ve already had to explain the Jolly Wrencher to your shoulder-surfing colleagues. And then to a hackspace or back to your home lab, stopping by the skull-and-cross-wrenches while commuting, naturally. You don’t bleed red, but rather #F3BF10. It’s time we talked.

The Hackaday writing crew goes to great lengths to cover all that is interesting to engineers and enthusiasts. We find ourselves stretched a bit thin and it’s time to ask for help. Want to lend a hand while making some extra dough to plow back into your projects? We’re looking for contributors to write a few articles per week and keep the Hackaday flame burning.

Contributors are hired as private contractors and paid for each article. You should have the technical expertise to understand the projects you write about, and a passion for the wide range of topics we feature. You’ll have access to the Hackaday Tips Line, and we count on your judgement to help us find the juicy nuggets that you’d want to share with your hacker friends.

If you’re interested, please email our jobs line (jobs at hackaday dot com) and include:

  • One example article written in the voice of Hackaday. Include a banner image, between 150 and 300 words, the link to the project, and any in-links to related and relevant Hackaday features. We need to know that you can write.
  • Details about your background that make you a valuable addition to the team. What do you like, and what do you do?
  • Links to your blog / project posts / etc. that have been published on the Internet, if any.
  • Or just write us with questions. We’ll be glad to answer.

Ladies and Gentlemen, start your applications!

The FM-1: Open Source Hacked Open, Vibe Coding, And Farting Synthesizers

The M-Vave FM-1 was a pretty unremarkable little synthesizer “toy” until the open-source synth hackers took it over. Now, it’s a sweet platform for exploration, the incredible work done by the community has encouraged the manufacturer to release an open SDK, and it has recently taken the global synth nerd community by storm. (It has sadly also gotten about a 50% markup in the last month due to this popularity.)

It’s the perfect storm of inexpensive hardware, vibe-coded software, and easy-to-use tooling that enables synthesizer firmware-hacking for the mainstream. It is also the fashionable box of the moment in a nerdy niche of the synthesizer world at the moment and it’s something that we’re going to see in non-synthesizer contexts as well, so buckle up.

Continue reading “The FM-1: Open Source Hacked Open, Vibe Coding, And Farting Synthesizers” →

How Metal Foam Could Make Cars Safer

Once upon a time, cars were merely designed for performance, comfort, and usability, with little regard to how safe they may or may not be in the event of a collision. In this era, it turned out that most cars were horrific deathtraps, but eventually outside pressure led the industry to try and make cars safer. It was realized that making crashes more survivable with less injuries was generally a good thing.

Ever since, there has been a general push towards making cars ever safer as time goes on. To that end, researchers have been exploring whether the use of metal foams could aid in further crash safety improvements.

Continue reading “How Metal Foam Could Make Cars Safer” →

Hackaday Links Column Banner

Hackaday Links: November 15, 2026

Another Hackaday Supercon is in the history books. The new venue was amazing. We had more attendees than ever and still had room to spare. You can find many of the talks, including the lightning talks, in the live section of our YouTube channel. You can even watch the final badge hacking competition.

Continue reading “Hackaday Links: November 15, 2026” →

Hackaday Podcast Episode 394: Linux In Weird Places, Yet More Hidden SDRs, And A Supercon Wrapup

Hackaday Editors Elliot Williams and Tom Nardi are back from Supercon, and they’ve got plenty of thoughts to share about it. But before they discuss this weekend’s higlights, they’ll cover the recent scuttling of the legendary SS United States, the discovery of even more hidden software-defined radios in everyday gadgets, Linux running on Kindles and microcontrollers, and a Game Boy flash cart that’s not designed for playing games. You’ll also hear about LEGO 3D printers, finding out where a video was recorded by the sound of the airplanes in the background, and a website that lets you listen in on the satellites flying over your house.

Check out the links if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download, DRM-free MP3.

Continue reading “Hackaday Podcast Episode 394: Linux In Weird Places, Yet More Hidden SDRs, And A Supercon Wrapup” →

This Week In Security: Four-Digit Patch Tuesday, SSH Exploited, GitBook Breach, Android GhostMap

It’s the second Tuesday of the month, and that means another Microsoft Patch Tuesday. The new normal is that the numbers are hard to believe. Brian Krebs reports that this month’s release fixes nearly 1,100 vulnerabilities, 63 of them rated critical, and over 500 that let an attacker elevate their privileges. Only one is reported as actively exploited: CVE-2026-124194, a spoofing bug in Outlook. Microsoft has now shipped more than 5,100 security fixes this year, after more than 1,400 last month, compared to an average of around 100 a month last year. Obviously AI tools get the credit for the volume of bugs fixed, but also of course for the volume of bugs found.

Everyone else is busy too. Apple pushed out-of-cycle updates for at least nine vulnerabilities across its operating systems, including an iMessage flaw which could let a remote attacker join a group chat and read its messages, and backported the fixes to iOS 18. Chrome 157 fixes CVE-2026-125350, another Chrome zero-day, a week after a Chrome release which fixed more than 200 bugs, Firefox 160 fixes almost 100 CVEs, and Adobe fixed more than 110.

Also since last week, zlib 1.4 shipped with more than a dozen security fixes, eight more vulnerabilities were disclosed in the X.Org server and XWayland, and Microsoft’s own Azure Linux update lists more than 470 CVEs fixed across the open source packages it ships. And for a perfect encapsulation of 2026, last month’s Patch Tuesday included a remote code execution bug in Windows Paint (CVE-2026-83844), though its description admits the code runs locally. So now I guess you can pop Calc through Paint? Does this count as a win?

Despite the absolute firehose of vulnerabilities, the Krebs article notices that of the roughly 95,000 CVEs assigned this year, only around 200 made it into the CISA list of known expoited vulnerabilities (KEV). If you have to pick and choose which updates are the most critical, start there.

Continue reading “This Week In Security: Four-Digit Patch Tuesday, SSH Exploited, GitBook Breach, Android GhostMap” →