AI-assisted Java4Shell discovery prompts patches and product rollout checks
Edited and reviewed by AI Ping Editorial Team
3-line summary
- Calif disclosed a Java flaw found with Codex assistance; Oracle included a fix on November 17.
- Exposure depends on runtime, CPU and settings, including Java copies bundled inside products.
- Keycloak is preparing updated images; PaperCut targets the week of November 23 for its maintenance release.
Calif has disclosed Java4Shell, a Java runtime vulnerability it found with help from Codex, while Oracle included a fix in its November 17 security update. On November 18, software developers including Keycloak and PaperCut detailed which deployments were exposed and how their own fixes were progressing.
Sophos identifies unpatched Java 17 builds from 17.0.6, plus the 21, 25 and 27 lines, as affected. Operators need to check the Java runtime, processor and settings. Microsoft says exposure requires untrusted data to reach the affected Base64 decoder on x86-64 hardware exposing AVX-512 VBMI. Base64 represents binary data as text. ARM64 and x86-64 processors without those instructions are outside the currently known affected configurations.
Calif says researcher Quang Luong spent about an hour finding the flaw and another two developing the first working demonstration, using less than $200 in tokens. The researcher selected audit areas; the team subsequently directed agents using its own tools and strategies. Those time and cost figures are Calif's account.
Oracle classifies the issue as remotely exploitable without authentication and assigns it an 8.1 score under CVSS 3.1, with high confidentiality, integrity and availability impacts. Its matrix identifies affected Java SE and certain GraalVM builds. Oracle provides security patches for supported product versions and says releases outside support are not tested for these vulnerabilities.
Amazon released Corretto 25.0.5.1.2 on November 17. Its changelog explicitly lists Java4Shell among the fixed vulnerabilities, and its release page provides Linux, Windows and macOS downloads. Product-specific packages and container rebuilds are following their suppliers’ own rollout schedules.
The bundled runtime determines product exposure
Keycloak's notice, updated at 09:29 UTC on November 18, identifies affected OpenJDK 21.0.13 builds inside container images 26.8.2-1 and 26.8.2-2. Whether those deployments are exposed also depends on the host processor and effective runtime settings. Keycloak uses the decoder before authentication.
Its team includes failover machines and rolling-update nodes in the assessment. The interim response disables accelerated decoding and restarts each process. The live JVM settings need verification after restart. At publication of its notice, Keycloak could not recommend a specific confirmed-fixed image tag.
Microsoft has published Azure Web Application Firewall custom-rule examples intended to detect and block known HTTP exploitation patterns while runtime updates are applied. Microsoft describes the filtering as an additional protective layer during patching.
Sophos's November 18 advisory includes Java runtimes bundled in third-party products within the scope of systems that operators manage themselves. Applications must restart after installation to load the patched runtime. Sophos said it was unaware of public reports of exploitation in the wild at that point.
PaperCut identifies its NG/MF Application Servers and Site Servers as affected on the relevant hardware. Versions 25.0.0 through 25.0.13 and 26.0.0 through 26.0.6 bundle affected Java builds. It lists version 24.x and earlier, along with cloud products Hive and Pocket, outside the affected product range.
PaperCut says its interim configuration can be kept in the product's custom directory so that it survives upgrades. Because that change disables the vulnerable accelerated path, scanners may continue to flag the installed Java build. The company is targeting the week beginning November 23 for a maintenance release containing fixed Java.
Sources
- Java4Shell: Write once, RCE everywhere — Calif
- Oracle Critical Security Patch Update Advisory — November 2026 — Oracle
- Addressing Java4Shell CVE-2026-114938: upgrade guidance and Azure WAF mitigations — Microsoft
- Java4Shell: What Keycloak admins need to do (CVE-2026-114938) — Keycloak
- Advisory: OpenJDK Base64 Vulnerability — Java4Shell (CVE-2026-114938) — Sophos
- Security Advisory: Java vulnerability Java4Shell (CVE-2026-114938) — PaperCut
- Corretto 25.0.5.1.2 release notes and fixed vulnerabilities — Amazon Corretto