Apocalypse now? Nice try!
I thought this is how it starts, but apparently nothing started. Too pathetic for a drill for the Apocalypse. Nonetheless, I asked Perplexity to make a quick summary of what seemed to be the beginning of the end:
Here’s a succinct timeline of the week’s disruptions, Thursday 12 November through Tuesday 17 November 2026. The events were not all confirmed as one coordinated cyberattack; several were attributed to technical failures or maintenance.
Date Event Thu, 12 A major Microsoft outage disrupted Outlook, Teams, Copilot and other Microsoft 365 services; Microsoft later attributed it to a network-capacity-upgrade issue, not a cyberattack. cbc Fri, 13 The FAA issued a nationwide ground stop lasting more than four hours after a technical problem, disrupting over 10,000 flights. cnbc Mon, 16 Major U.S. banks, including JPMorgan Chase, U.S. Bank and Wells Fargo, had online-access and transaction problems; United Airlines also had a technology failure that delayed roughly 150 flights. newsnationnow Mon, 16 Attackers exploited Optimizely’s Web Experimentation platform to inject malicious JavaScript into 188 scripts used by 178 organisations, including the BBC, CNN, Apple, Salesforce, HSBC, Equifax, IKEA, Zoom and TalkTalk. The code aimed to steal cryptocurrency, card details and cookies, and deliver iOS exploit code. newsweek Mon, 16 RIKEN announced that Fugaku, Japan’s most powerful supercomputer, had likely been breached. Suspicious communications were detected on 12 November; unauthorized access occurred from 10–13 November, and the system was paused early on 14 November after tampering was confirmed on some servers. japantimes.co Tue, 17 The NSA’s internal classified-communications network went offline. The agency described it as “temporary degradation during scheduled routine maintenance”; mission-critical capabilities reportedly remained operational. cnn Tue, 17 Apple services, including iCloud and Apple Pay, were disrupted. Apple said the cause was an internal update, not a cyberattack. bbc Tue, 17 Java4Shell (CVE-2026-114938) was disclosed: a memory-corruption flaw in OpenJDK’s hardware-accelerated Base64 decoder that could permit unauthenticated remote code execution on affected x86-64 systems with AVX-512. Oracle and OpenJDK released fixes the same day. azul The Microsoft, FAA, bank, United, Apple and NSA incidents were reported as outages or technical/maintenance problems—not necessarily cyberattacks. The Optimizely incident and the Fugaku intrusion were confirmed or strongly indicated security compromises. bbc
I’m not impressed. The Apocalypse stopped!
As for Java4Shell, it somehow seems less severe than PHP2Shell.
Malwarebytes: Java4Shell: A critical flaw with a narrow reach:
A critical-sounding Java flaw is making headlines. Most consumers are unlikely to be affected, but companies running Jira, Confluence, Jenkins and similar tools have work to do.
On November 17, Oracle and the OpenJDK project shipped fixes for CVE-2026-114938, a memory-corruption bug in Java’s Base64 decoder. Security firm Calif discovered the flaw and named it Java4Shell. CISA urged organizations to patch immediately.
After a run of high-profile computer problems and security scares, it’s understandable that another vulnerability with a catchy name would set alarm bells ringing. But it’s important to separate the potential damage from the likelihood of being affected. This is a serious issue for organizations running vulnerable applications, not a reason for every home user to assume their computer is at risk.
It doesn’t help that organizations give out different CVSS scores for the same vulnerability.
- Oracle rates it 8.1 under CVSS 3.1 and describes it as “difficult to exploit.”
- Calif rates it 9.2 (Critical) under CVSS 4.0.
Meanwhile, there are currently no reports of abuse in the wild. Calif demonstrated remote code execution without logging in on default installations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. It also demonstrated post-login code execution on Kafka, Solr, Elasticsearch, Gerrit and Spinnaker.
So, if we’re to believe them, Java4Shell is not as apocalyptic as most tech websites make it look. The bad news is that the bug is in the Base64 decoder of OpenJDK. The good news is that it only affects x86-64 CPUs that support the AVX-512 VBMI instruction set. ARM64 chips are safe.
Red Hat rates CVE-2026-114938 9.8 under CVSS v3.
As I am writing this, Debian fixed CVE-2026-114938 only in sid.
OTOH, Oracle released fixed builds on November 17, and Amazon released a fixed Corretto the same day. If a patch is not available for your OpenJDK, there are two workarounds (use only one of them): -XX:-UseBASE64Intrinsics (preferred) or -XX:UseAVX=2 (Intel/AMD-only). The second option has a heavier impact on speed.
The Apocalypse failed to materialize. Also, the Four Horsemen seemed to have enjoyed the weekend. No unpaid overtime!

Leave a Reply