<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jvm on Kuldeep Pisda</title><link>https://kdpisda.in/tag/jvm/</link><description>Recent content in Jvm on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 21 Nov 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/jvm/index.xml" rel="self" type="application/rss+xml"/><item><title>Java4Shell's Stopgap Flags: Two Can Stop Your JVM, One Can Quietly Miss It</title><link>https://kdpisda.in/java4shell-mitigation-flags-jvm-startup-launcher-env/</link><pubDate>Sat, 21 Nov 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/java4shell-mitigation-flags-jvm-startup-launcher-env/</guid><description>&lt;p&gt;&lt;a href="https://calif.io/java4shell"&gt;CVE-2026-114938&lt;/a&gt;, which its finders named Java4Shell, is an out-of-bounds write in HotSpot&amp;rsquo;s x86-64 Base64 decode intrinsic. Oracle and the OpenJDK updates project shipped fixed builds on November 17 (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1). Not every vendor has caught up. Red Hat&amp;rsquo;s &lt;a href="https://access.redhat.com/security/vulnerabilities/RHSB-2026-018"&gt;bulletin&lt;/a&gt;, last updated November 20, still lists no fixed packages and says only that it is &amp;ldquo;expediting the release of fixes.&amp;rdquo; If you run RHEL or UBI-based Java images, or a product that bundles its own JRE, the thing standing between you and the bug this week is a JVM flag.&lt;/p&gt;</description></item></channel></rss>