{"id":26332,"date":"2026-11-19T12:00:09","date_gmt":"2026-11-19T20:00:09","guid":{"rendered":"https:\/\/www.palada.net\/index.php\/2026\/11\/19\/java4shell-is-inside-the-software-you-run-can-you-find-every-copy\/"},"modified":"2026-11-19T12:00:09","modified_gmt":"2026-11-19T20:00:09","slug":"java4shell-is-inside-the-software-you-run-can-you-find-every-copy","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2026\/11\/19\/java4shell-is-inside-the-software-you-run-can-you-find-every-copy\/","title":{"rendered":"Java4Shell is inside the software you run. Can you find every copy?"},"content":{"rendered":"<div class=\"rich-text_richText__UyrDZ\" data-anchor-headings=\"true\" data-component=\"rich-text\" data-reader-view=\"false\">\n<div class=\"payload-richtext\">\n<p>On Nov. 17, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) <a href=\"https:\/\/www.cisa.gov\/news-events\/alerts\/2026\/11\/17\/critical-java-vulnerability-requires-immediate-patching\"><span style=\"text-decoration:underline\">urged organizations to patch<\/span><\/a> CVE-2026-114938 immediately, with researchers calling it Java4Shell. It is a memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine (JVM), and specially crafted input can crash the JVM or allow unauthenticated remote code execution.<\/p>\n<p>The patch is the easy part to describe. CISA&#8217;s first instruction is harder: identify affected Java installations, including runtimes bundled with third-party applications or included in container images and appliances.<\/p>\n<p>Most organizations know which Java they installed. Far fewer know which Java their vendors installed for them.<\/p>\n<h3><strong>What is Java4Shell (CVE-2026-114938)?<\/strong><\/h3>\n<p>Java4Shell sits in hand-written assembly that HotSpot uses to speed up Base64 decoding on x86-64 processors with AVX-512 VBMI support. According to <a href=\"https:\/\/calif.io\/java4shell\"><span style=\"text-decoration:underline\">Calif<\/span><\/a>, the research firm that found it, 64 &#8220;A&#8221; characters followed by a single &#8220;=&#8221; make that routine write 62 bytes past the end of its output array. Java rejects the input, but by then neighboring objects in memory may already be corrupted.<\/p>\n<p>What we know as of Nov. 18:<\/p>\n<ul class=\"list-bullet\">\n<li class=\"\" value=\"1\"><strong>Affected software:<\/strong> OpenJDK builds from 17.0.6 onward, including Java 21, 25 and 27, that predate the Nov. 17 fixes, and the distributions built from them: Amazon Corretto, Eclipse Temurin, Azul Zulu, BellSoft Liberica, Microsoft Build of OpenJDK, Red Hat build of OpenJDK, SAP SapMachine, Oracle OpenJDK and Oracle GraalVM for JDK, among others. Oracle also lists one Java 8 build, Oracle Java SE 8u511b33-perf.<\/li>\n<li class=\"\" value=\"2\"><strong>Affected hardware:<\/strong> x86-64 CPUs with AVX-512 VBMI, such as Intel Xeon Ice Lake and later, and AMD Zen 4 and later. ARM64 systems are not affected.<\/li>\n<li class=\"\" value=\"3\"><strong>Impact:<\/strong> Researchers demonstrated unauthenticated remote code execution in default configurations of Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.<\/li>\n<li class=\"\" value=\"4\"><strong>Severity:<\/strong> Oracle scores it 8.1 under CVSS 3.1. The researchers score it 9.2 under CVSS 4.0.<\/li>\n<li class=\"\" value=\"5\"><strong>Fixes:<\/strong> Oracle&#8217;s <a href=\"https:\/\/www.oracle.com\/security-alerts\/cspunov2026.html\"><span style=\"text-decoration:underline\">November Critical Security Patch Update<\/span><\/a> and an <a href=\"https:\/\/openjdk.org\/groups\/vulnerability\/advisories\/2026-11-17\"><span style=\"text-decoration:underline\">OpenJDK advisory<\/span><\/a>, both released Nov. 17.<\/li>\n<li class=\"\" value=\"6\"><strong>Exploitation:<\/strong> No in-the-wild exploitation had been reported as of this writing.<\/li>\n<\/ul>\n<p>One detail should get every security leader&#8217;s attention. The researcher who found the bug used an AI coding agent, took about an hour to find it and two more to build a first working exploit, and spent less than $200 in tokens. There is no universal exploit as yet, however, this doesn\u2019t mean defenders get extra patching time. As RL threat researcher Zaria Vuksan <a href=\"https:\/\/www.reversinglabs.com\/blog\/the-sky-is-falling-again-what-php2shell-says-about-ai-the-disclosure-process-and-security\"><span style=\"text-decoration:underline\">documented<\/span><\/a>, when PHP2Shell technical details were posted to security forums before the agreed disclosure date, it led to panic and early exploitation attempts before the patch was out.\u00a0<\/p>\n<h3><strong>Every year, the same story<\/strong><\/h3>\n<p>If the name sounds familiar, that&#8217;s the point. Java4Shell is the latest in a run of critical remote code execution flaws hiding in software almost everyone runs.<\/p>\n<\/p>\n<div class=\"lexical-table-container\">\n<table class=\"lexical-table\" style=\"border-collapse:collapse\">\n<tbody>\n<tr class=\"lexical-table-row\">\n<th class=\"lexical-table-cell lexical-table-cell-header-1\" style=\"border:1px solid #ccc;padding:8px\">\n<p>When<\/p>\n<\/th>\n<th class=\"lexical-table-cell lexical-table-cell-header-1\" style=\"border:1px solid #ccc;padding:8px\">\n<p>Name<\/p>\n<\/th>\n<th class=\"lexical-table-cell lexical-table-cell-header-1\" style=\"border:1px solid #ccc;padding:8px\">\n<p>Where it hid<\/p>\n<\/th>\n<\/tr>\n<tr class=\"lexical-table-row\">\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>December 2021<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>Log4Shell (CVE-2021-44228)<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>A logging library<\/p>\n<\/td>\n<\/tr>\n<tr class=\"lexical-table-row\">\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>March 2022<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>Spring4Shell (CVE-2022-22965)<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>A web framework<\/p>\n<\/td>\n<\/tr>\n<tr class=\"lexical-table-row\">\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>December 2025<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>React2Shell (CVE-2025-55182)<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>A UI framework<\/p>\n<\/td>\n<\/tr>\n<tr class=\"lexical-table-row\">\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>October 2026<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p><a href=\"https:\/\/www.reversinglabs.com\/php2shell-detection\"><span style=\"text-decoration:underline\">PHP2Shell<\/span><\/a> (CVE-2026-109618, CVE-2026-109619)<\/p>\n<\/td>\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>The PHP language runtime<\/p>\n<\/td>\n<\/tr>\n<tr class=\"lexical-table-row\">\n<td class=\"lexical-table-cell lexical-table-cell-header-0\" style=\"border:1px solid #ccc;padding:8px\">\n<p>October 2026<\/p>\n<\/td>\n<p><template id=\"P:1d\"><\/template><template id=\"P:1e\"><\/template><\/tr>\n<p><template id=\"P:1f\"><\/template><\/tbody>\n<\/table>\n<\/div>\n<p>Look at the right-hand column. The last three sit deeper than any before them: inside the language runtimes that run everything else.<\/p>\n<p>Log4j was a dependency, so it usually showed up in build files and JAR files. It was painful to track down, especially if you didn\u2019t already have a binary-derived set of SBOMs to search for vulnerable components.\u00a0\u00a0<\/p>\n<p>Node2Shell lived in the Brotli decoder that Node.js compiles in, and <a href=\"https:\/\/www.akamai.com\/blog\/security-research\/inside-node2shell-closer-look-cve-2026-111497\"><span style=\"text-decoration:underline\">Akamai notes<\/span><\/a> that applications were exposed through fetch() and Express 5 without ever calling Brotli directly. Java4Shell lives in the JVM&#8217;s own machine code.<\/p>\n<p>Nobody declares a Java runtime in a pom.xml. It just comes with the software.\u00a0<\/p>\n<h3><strong>Why bundled Java runtimes are so hard to find<\/strong><\/h3>\n<p>CISA&#8217;s guidance points at the right problem. Java rarely runs only where your team installed it. It also runs in:<\/p>\n<ul class=\"list-bullet\">\n<li class=\"\" value=\"1\"><strong>Vendor applications<\/strong> that ship a private Java runtime in their own install directory.<\/li>\n<li class=\"\" value=\"2\"><strong>Container base images<\/strong> that may not have been rebuilt in months.<\/li>\n<li class=\"\" value=\"3\"><strong>Virtual appliances and VM images<\/strong> delivered by vendors as finished products.<\/li>\n<li class=\"\" value=\"4\"><strong>The tools that build and store your software.<\/strong> Jenkins and JFrog Artifactory are both on the list of demonstrated targets.<\/li>\n<\/ul>\n<p>Common inventory methods can miss them. Manifest-based software composition analysis reads the dependencies a project declares, and a runtime isn&#8217;t declared. Installed-software lists may show what the operating system&#8217;s package manager put on the machine but not a runtime a vendor unpacked into its own folder. Even when you find a runtime, the version string depends on who built it: Oracle, Amazon, Red Hat and the Linux distributions each label fixed builds differently.That makes Java4Shell a software supply chain security problem as much as a patching problem.\u00a0<\/p>\n<p>Bundled runtimes are one example of a broader gap we&#8217;ve measured. When we analyzed 44 complete software packages and compared what we found with each package&#8217;s own manifest, the manifests missed an average of 49.91% of the components actually present, as our <a href=\"https:\/\/www.reversinglabs.com\/manifest-report\"><span style=\"text-decoration:underline\">Manifest Misconceptions report<\/span><\/a> details. In the compromised SolarWinds Orion package behind the Sunburst attack, the manifest listed 505 items, and the full package held 50,265. In an old 3CX release, the malware sat in components the manifest never listed. Declarations, questionnaires and version labels tell you what someone believes is inside. The binary tells you what actually is. When the question is &#8220;where is the vulnerable JVM,&#8221; only the second answer counts.<\/p>\n<h3><strong>Patching is step two. Proving the patch is step three.<\/strong><\/h3>\n<p>Detection has outrun remediation, and flaws inside the runtime make that gap harder to close. For the Java you installed, patching means updating the runtime and restarting every JVM. For the Java your vendors bundled, you usually can&#8217;t patch it yourself. You wait for each vendor to ship an update with a fixed runtime inside.<\/p>\n<p>When that update arrives, it&#8217;s usually trusted because the release notes say it fixes the issue. That&#8217;s the same kind of trust attackers exploited when they rode vendor update channels into SolarWinds and 3CX customers. An urgent update tends to be installed fastest and checked least.<\/p>\n<p>So check it. Compare the new version with the one you&#8217;re running. Did the Java runtime actually change, and to which build? Did anything else change that shouldn&#8217;t have? Those answers are in the difference between two versions, and you can get them before you deploy.<\/p>\n<p>There&#8217;s a second reason to move fast. ReversingLabs CEO Mario Vuksan argues in <a href=\"https:\/\/www.reversinglabs.com\/resources\/the-patch-is-the-attack-payload\"><span style=\"text-decoration:underline\">The Patch Is the Attacker&#8217;s Blueprint<\/span><\/a> that AI has collapsed the exploit window, and that every published patch can give attackers a map of what changed and where to look. Java4Shell was found for less than $200. Now the fix points every other attacker to the same code. As RL&#8217;s PHP2Shell analysis notes, attackers can build exploits by comparing builds from before and after a patch.<\/p>\n<h3><strong>What to do about Java4Shell this week<\/strong><\/h3>\n<p><strong>If you run software<\/strong> (and every organization does):<\/p>\n<ol class=\"list-number\">\n<li class=\"\" value=\"1\"><strong>Inventory every Java runtime,<\/strong> including those bundled in third-party applications, container images, VM images and appliances. Also look for Java that makes outbound connections, such as agents, integrations and build tools, since a Java program that opens a TLS connection to a malicious server can be compromised even if it exposes no service of its own.<\/li>\n<li class=\"\" value=\"2\"><strong>Check the hardware.<\/strong> Only x86-64 processors with AVX-512 VBMI are affected, which helps you prioritize.<\/li>\n<li class=\"\" value=\"3\"><strong>Patch, then restart<\/strong> every affected JVM, and re-run the inventory to confirm the running build changed.<\/li>\n<li class=\"\" value=\"4\"><strong>If you can&#8217;t patch yet,<\/strong> the researchers recommend starting OpenJDK with -XX:-UseBASE64Intrinsics, or with -XX:UseAVX=2 on x86-64 hosts only. CISA also recommends validating Base64 input at the application boundary, enforcing input-size limits and limiting unauthenticated access.<\/li>\n<li class=\"\" value=\"5\"><strong>Ask each vendor<\/strong> which Java build their product ships, when the fix lands and how they verify their update before it reaches you.<\/li>\n<li class=\"\" value=\"6\"><strong>Verify vendor updates before you deploy them.<\/strong> Confirm the new version contains a fixed runtime and nothing unexpected.<\/li>\n<\/ol>\n<p><strong>If you build software:<\/strong><\/p>\n<ol class=\"list-number\">\n<li class=\"\" value=\"1\"><strong>Find every Java runtime you ship,<\/strong> including bundled runtimes, custom runtime images and container base images.<\/li>\n<li class=\"\" value=\"2\"><strong>Rebuild on a fixed build<\/strong> and verify the release artifact itself, not just the build configuration, contains it.<\/li>\n<li class=\"\" value=\"3\"><strong>Tell customers exactly<\/strong> which runtime build is in which release. They are about to ask.<\/li>\n<\/ol>\n<h3><strong>Don&#8217;t star in the sequel<\/strong><\/h3>\n<p>Java4Shell will get patched, and the cleanup will take longer than anyone wants. Then there will be another one. AI has made finding these flaws cheap, and the next one may sit even deeper in the stack.<\/p>\n<p>The organizations that handle the sequel well will be the ones that can answer two questions fast. Where does this component actually run, including inside software we bought? And what evidence do we have that the update fixed it?<\/p>\n<p>Those answers come from the software itself, not the manifest, the questionnaire or the release notes. That&#8217;s why we recommend scanning the compiled binaries and the full install package of any software deployed in your environment.<\/p>\n<p><em>When PHP2Shell hit last month, RL Spectra Assure\u00ae added <\/em><a href=\"https:\/\/www.reversinglabs.com\/php2shell-detection\"><span style=\"text-decoration:underline\"><em>PHP2Shell detection<\/em><\/span><\/a><em>, finding embedded PHP components and their versions inside commercial applications and other third-party software. The same binary analysis works without source code across compiled software, container images and VM disk images, and <\/em><a href=\"https:\/\/www.reversinglabs.com\/solutions\/secure-virtual-machine-images\"><span style=\"text-decoration:underline\"><em>pre-deployment VM analysis<\/em><\/span><\/a><em> checks those images without deploying them.<\/em>\u00a0 <a href=\"https:\/\/www.reversinglabs.com\/products\/spectra-assure\"><span style=\"text-decoration:underline\"><em>Learn more about Spectra Assure<\/em><\/span><\/a><em>.<\/em><\/p>\n<h3><strong>Java4Shell FAQ<\/strong><\/h3>\n<p><strong>What is Java4Shell?<\/strong> <br \/>Java4Shell (CVE-2026-114938) is a memory-corruption vulnerability in the x86-64 Base64 decoder of OpenJDK&#8217;s HotSpot JVM. Crafted Base64 input can crash the JVM or allow unauthenticated remote code execution. CISA issued an alert urging immediate patching on Nov. 17, 2026.<\/p>\n<p><strong>Am I affected by Java4Shell?<\/strong> <br \/>You may be if you run an OpenJDK build from 17.0.6 onward that predates the Nov. 17 fixes, or a distribution built from one, on an x86-64 processor with AVX-512 VBMI. ARM64 systems are not affected. Check runtimes bundled in vendor software, containers and appliances, not just the ones you installed. You may be if you run a Java runtime built from OpenJDK 17.0.6 or later, including Java 21, 25 and 27, that predates the Nov. 17 fixes, on an x86-64 processor with AVX-512 VBMI. That covers most major distributions, including Amazon Corretto, Eclipse Temurin, Azul Zulu, BellSoft Liberica, Microsoft Build of OpenJDK, Red Hat build of OpenJDK, SAP SapMachine and Oracle OpenJDK. Red Hat says OpenJDK 8 and 11 don&#8217;t contain the vulnerable code, but Oracle lists one Java 8 build as affected: Oracle Java SE 8u511b33-perf. ARM64 systems are not affected. Check the researchers&#8217; affected-products list, Oracle&#8217;s November 2026 Critical Patch Update and your provider&#8217;s advisory, such as Red Hat&#8217;s or Amazon Linux&#8217;s. Include runtimes bundled in vendor software, containers and appliances, not just the ones you installed.<\/p>\n<p><strong>Is Java4Shell being exploited?<\/strong> <br \/>No in-the-wild exploitation had been reported as of Nov. 18, 2026. Researchers have demonstrated working exploits against several widely used Java applications.<\/p>\n<p><strong>How is Java4Shell different from Log4Shell?<\/strong> <br \/>Log4Shell was in a logging library that applications declared as a dependency. Java4Shell is in the Java runtime itself, so it can affect any Java application on an affected build and processor that decodes attacker-supplied Base64, whether or not the team knew Java was there.<\/p>\n<p><strong>How do I find Java runtimes bundled in third-party software?<\/strong> <br \/>Dependency manifests and installed-software lists can miss them. Analyze the software, container images and VM images themselves to see which runtime files they contain, then match those builds to vendor advisories.<\/p>\n<p><strong>What is Node2Shell?<\/strong> <br \/>Node2Shell (CVE-2026-111497) is an out-of-bounds write in the Brotli decoder bundled with Node.js, fixed in October 2026 in Node.js 22.23.4, 24.22.1 and 26.12.1. Like Java4Shell, it sits inside the runtime rather than in application code.<\/p>\n<\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>On Nov. 17, the U.S. Cybersecurity and Infrastructure Security Agency (CISA)urged organizations to patchCVE-2026-114938 immediately, with researchers calling it Java4Shell. It is a memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine (JVM), and specially crafted input can crash the JVM or allow unauthenticated remote code execution.The patch is the easy part to describe. CISA&#8217;s first instruction is harder: identify affected Java installations, including runtime<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[32775],"tags":[],"class_list":["post-26332","post","type-post","status-publish","format-standard","hentry","category-reversinglabs"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/26332","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=26332"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/26332\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=26332"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=26332"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=26332"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}