Friday, 20 November 2026

Pakistan’s National CERT Urges Immediate Java4Shell Security Updates

National CERT tells Pakistani organisations to patch Java now: a flaw called Java4Shell lets attackers take over servers, and fixes came on 17 November.

Key points

  • National CERT rates Java4Shell (CVE-2026-114938) as critical, 9.2, with no login needed.
  • Oracle and other vendors released fixes on 17 November.
  • Only x86-64 chips with AVX-512 VBMI are affected; ARM64 is not.

Pakistan’s National CERT has told government bodies and private companies to update Java on their servers straight away. The flaw, named Java4Shell, lets an attacker run code on a server without logging in, which can mean losing the whole machine.

The advisory covers CVE-2026-114938 in OpenJDK, the open-source base of most Java runtimes. It carries a critical severity score of 9.2. For ordinary readers this matters indirectly: banks, telecom systems and web services in Pakistan run on Java, and a hijacked server is how customer data leaks start.

A single badly formed Base64 string is enough to trigger it, and many Java apps decode such strings before they know who is calling. Because so many programs decode Base64 early, National CERT’s advisory says they hit the faulty code before any password check. It only affects x86-64 chips with AVX-512 VBMI support. ARM64 machines such as AWS Graviton and Macs with Apple chips are safe.

Fixes were released on 17 November in Oracle’s November critical patch update. On Oracle’s side, Java 17 needs 17.0.21.1, Java 21 needs 21.0.13.1, Java 25 needs 25.0.5.1 and Java 27 needs 27.0.1.1.

Other vendors ship their own matching releases. Amazon Corretto, Eclipse Temurin, Microsoft’s OpenJDK build, Azul Zulu, BellSoft Liberica, SAP SapMachine and the Red Hat build are all affected, and each vendor has its own fixed build.

Researchers found Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate vulnerable before login in their default setups. Exploitation was also shown on Spring Boot, Struts, Tomcat and Jetty. Kafka, Solr, Elasticsearch, Gerrit and Spinnaker are exposed only after login.

As we previously reported, the vulnerability was discovered with AI assistance in approximately one hour before researchers developed a working exploit.

National CERT’s advice is to patch internet-facing Java applications first, and to patch every host, including Java bundled inside other products, since updating an application does not fix the runtime under it.

Until a server is patched, the optimised Base64 routine can be switched off with a JVM flag named in the OpenJDK and vendor notices, but the advisory says to confirm the exact flag for your build. After patching, administrators are told to go through their logs for strange requests, cut off any machine that looks compromised and report confirmed incidents to the authorities.

A compromised Java server can become a stepping stone into internal systems. The advisory also suggests limiting internet exposure and putting a web application firewall in front of servers.

When the advisory was written, nobody had reported real-world attacks or a public exploit, and the US CISA exploited-flaws list did not include it yet. National CERT still expects attacks soon and says organisations should not wait to see one before patching.

The warning comes as attackers have begun probing vulnerable Java installations. In a separate report, security companies including GreyNoise, WatchTowr and Cloudflare identified scanning and attempted exploitation.

Although those observations do not establish successful compromises, they underline the importance of applying available updates without delay.

Zohaib Butt

Zohaib covers Pakistan for Tech Prolonged: telecom operators, PTA decisions, policy and digital banking. A software engineer who switched to Android early and never looked back, he has written for the site since its early years.