{
  "id": 20787148,
  "title": "The Java4Shell fix lives in the fourth version number",
  "url": "https://urgent.news/2026/11/19/the-java4shell-fix-lives-in-the-fourth-version-number",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-19T19:00:00.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/ianwieds/the-java4shell-fix-lives-in-the-fourth-version-number-3p26"
  },
  "original_language": "en",
  "account": "The Java4Shell security vulnerability, identified as CVE-2026-114938, affects certain versions of the Java Development Kit (JDK). The flaw exploits a heap overflow in the HotSpot JVM's Base64 decoder, potentially leading to remote code execution. Versions 17.0.6 and later are vulnerable, including JDKs 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1. The issue arises from a delay in handling a small Base64 input fragment within the decoder, allowing attackers to manipulate data and execute arbitrary code. Patch 8393212, introduced in JDK 17.0.21.1, resolves the problem by adjusting the Base64 decoder to handle the final fragment directly, eliminating the vulnerability. While some systems, like ARM-based laptops, are unaffected, users of vulnerable x86-64 systems with AVX-512 capabilities should upgrade to one of the patched versions to mitigate the risk.",
  "summary": "My laptop has two JDKs on Oracle's list of builds hit by Java4Shell: 27.0.1.0.3 and 21.0.13.0.3. Neither one can be hit. The builds that fix it are 27.0.1.1 and 21.0.13.1. Read those twice. The difference is one digit, in a slot a lot of version checks throw away. Java4Shell (CVE-2026-114938) went public on Tuesday from the security shop Calif, and it climbed to 623 points on Hacker News . It's a…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}