Skip to main content

What IT Teams Need to Know This Morning, Wednesday 18 November 2026: Java4Shell Splits Estates by Processor

Java4Shell only bites on servers with AVX-512 VBMI, CISA says a critical Puppet Enterprise flaw is exploited, Ipsos is investigating a cyber attack and the Commission has a preliminary finding against Temu.

A stunning cityscape showcasing skyscrapers during a vibrant sunset view.
KBY News Desk7 min read

In this article

Share

The item that matters most this morning is Java4Shell. Oracle and the OpenJDK project released fixes on Tuesday 17 November for CVE-2026-114938, a memory-corruption flaw in the way Java decodes Base64 text, and the firm that found it, Calif.io, says it can give an attacker code execution on products such as Jira, Confluence, Jenkins and Keycloak. It bites only on servers with a particular processor feature, which makes it one of the rare vulnerabilities you can partly triage with a hardware check. Below that, CISA has added a critical Puppet Enterprise flaw to its exploited list, the market research group Ipsos is investigating a cyber attack, and the European Commission has reached a preliminary finding against Temu. Microsoft Ignite continues in San Francisco.

#Our lead: look at the CPU flags before you look at the version

Most flaws are a question of software versions. This one has a hardware condition too. Calif says OpenJDK decodes Base64 with a hand-written routine built on AVX-512 VBMI instructions, that the bug sits in the code that handles the last few characters, and that on processors without those instructions Java takes a different path and never reaches the flaw. Calif lists the affected processor families as Intel Xeon from Ice Lake onwards and AMD EPYC and Ryzen parts from Zen 4 onwards, and says ARM64 is not affected. On Linux, the check Calif describes is a search of the CPU flags for avx512f, avx512bw, avx512vbmi and bmi2, all four of which must be present. In a virtual machine, run it inside the guest, because the flags are whatever the hypervisor passes through.

On the software side, Calif says OpenJDK 17.0.6 and newer is affected, and the OpenJDK Vulnerability Group’s advisory of 17 November covers the 17, 21, 25 and 27 lines. Calif says it demonstrated code execution before login, in default settings, on Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate. Those claims come from Calif’s own testing and we have not seen the vendors confirm them. Tenable said on Tuesday that it knew of no reports of exploitation, and the flaw is not in CISA’s Known Exploited Vulnerabilities catalogue, although The Register reports that CISA has urged Java users to patch immediately. Oracle scores the flaw 8.1 and Calif scores it 9.2; the gap reflects Oracle pricing in the hardware condition and the need for an application to pass untrusted data to the decoder.

Our view is that this will split estates in two. A mixed fleet of older on-premises servers may find only a few hosts qualify, while a fleet that moved to recent cloud instances may find most of them do, so do not assume either way. If you cannot patch today, Calif names two startup options that keep the vulnerable code from running, -XX:-UseBASE64Intrinsics and -XX:UseAVX=2. Tenable points out that neither Oracle nor the OpenJDK group mentions them, so test first and remove them once patched. Start with anything internet-facing or sitting in front of staff logins. Our full story has the fixed build numbers and the questions to put to your application vendors: Java4Shell: Patch OpenJDK Now, but First Check Whether Your Servers Have the Processor Feature It Needs.

#Since yesterday morning

#
CISA says a critical Puppet Enterprise flaw is being exploited

CISA added CVE-2026-115731, a flaw in the server side of Perforce Puppet Enterprise, to its Known Exploited Vulnerabilities catalogue on Tuesday 17 November. The CVE record, filed by Puppet’s own security team, says a client holding any certificate signed by the Puppet certificate authority can run code on the Puppet Server by sending a crafted report. It adds that where the authority signs requests automatically without strong verification, an unauthenticated attacker on the network can obtain such a certificate first. The record names fixed releases 2023.8.13, 2025.12.1 and 2026.0.1, and CISA’s due date for US federal agencies is Tuesday 1 December. Neither the catalogue entry nor the record says who is exploiting the flaw.

The practical point is the second sentence of the record. In our reading, a Puppet server is the machine that configures your other machines, so a compromise there could reach everything it manages. Before you plan the upgrade, check how your certificate authority decides which requests to sign, because open autosigning turns a flaw that needs a certificate into one that needs only network access. Our full story covers the affected versions and a second flaw published alongside it: CISA Says a Critical Puppet Enterprise Flaw Is Being Exploited, and Autosigned Certificates Make It Easier.

#
Ipsos is investigating a cyber attack on an internal system

Ipsos said in a statement issued from Paris on Monday 16 November that it has identified a cybersecurity incident affecting one internal information system and has filed a complaint with the relevant authorities. The headline of its release dates the complaint to Wednesday 11 November. The company says it activated its incident response procedures, took steps to contain the incident and engaged external specialists, and that the incident had no impact on its operations or its ability to deliver for clients. It says the investigation is continuing to establish the nature and scope of the incident, and that it will contact those concerned directly if the investigation establishes that information relating to clients, projects or business partners was affected.

What it has not said is whether any data was taken. The Register reports that Ipsos declined its requests for more detail because it does not want to release unverified information. That is a defensible position for a company in the middle of an investigation, and it also means nobody outside Ipsos can yet say who is affected. If your organisation commissions research from Ipsos, or your staff or customers took part in its surveys, we would ask your account contact in writing this week which systems and data sets are involved, whether any of your data is among them, and when you will be told. Nothing in the statement suggests you need to change anything on your own systems today.

#
The European Commission says Temu falls short on illegal products

The European Commission announced on Tuesday 17 November that it has preliminarily found Temu in breach of the Digital Services Act, in the obligation to put in place reasonable, proportionate and effective measures to mitigate the risk of illegal products being offered on its platform. In the Commission’s words, Temu’s mitigation measures include ineffective controls to check the compliance of products, a weak content moderation system and an ineffective sanction system. Executive Vice-President Henna Virkkunen said that “Shopping online should not mean risking the purchase of illegal and unsafe products.” The Register reports that a Temu spokesperson said the company respectfully disagrees and will review and respond to the findings.

A preliminary finding is not a final decision, and Temu has not been fined by this announcement. We include it because it shows how the regulator is testing platforms: not by whether a policy exists, but by whether the checks, moderation and penalties work in practice. If your organisation runs a marketplace, a user-generated content service or any platform with notice-and-action duties, the useful exercise is to ask whether your own controls would survive that kind of examination.

#Today

Microsoft Ignite runs from 17 to 20 November. We will publish our day-two digest this evening, covering only what an admin has to act on or plan for.

#Three things to do this morning

  1. List your Java-based identity, ticketing, build and repository servers, and check each host’s CPU flags for avx512f, avx512bw, avx512vbmi and bmi2.
  2. If you run Puppet Enterprise, find out whether your certificate authority autosigns requests and which release you are on.
  3. If Ipsos is a supplier, send your account contact the three questions above and note the date you asked.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01Calif.io: Java4Shellcalif.io
  2. 02OpenJDK Vulnerability Group: advisory of 17 November 2026openjdk.org
  3. 03Oracle: Critical Security Patch Update, November 2026oracle.com
  4. 04Tenable: Java4Shell frequently asked questionstenable.com
  5. 05The Register: Oracle reveals fix-this-ASAP-grade Java4Shell bugtheregister.com
  6. 06CISA Known Exploited Vulnerabilities cataloguecisa.gov
  7. 07NVD: CVE-2026-115731services.nvd.nist.gov
  8. 08Ipsos: press release of 16 November 2026finanzwire.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on What IT Teams Need to Know This Morning, Wednesday 18 November 2026: Java4Shell Splits Estates by Processor. Comments are checked for spam and held for moderation before appearing.

Loading comments...

More news

All news

Was this useful?

Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.