<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>VULNERABILITY NEWS - Aqua</title>
	<atom:link href="https://www.aquasec.com/category/vulnerability-news/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Cloud Native Security, Container Security &#38; Serverless Security</description>
	<lastBuildDate>Wed, 18 Nov 2026 00:33:02 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>
	<item>
		<title>Java4Shell Vulnerability: How Should Security Teams Identify and Reduce Exposure?</title>
		<link>https://www.aquasec.com/blog/java4shell-vulnerability-how-should-security-teams-identify-and-reduce-exposure/</link>
		
		<dc:creator><![CDATA[Aqua Security]]></dc:creator>
		<pubDate>Tue, 17 Nov 2026 23:15:47 +0000</pubDate>
				<category><![CDATA[VULNERABILITY NEWS]]></category>
		<guid isPermaLink="false">https://www.aquasec.com/?p=28484</guid>

					<description><![CDATA[<div class="hs-featured-image-wrapper"><a href="https://www.aquasec.com/blog/java4shell-vulnerability-how-should-security-teams-identify-and-reduce-exposure/" title="Java4Shell Vulnerability: How Should Security Teams Identify and Reduce Exposure?" class="hs-featured-image-link"><img src="https://www.aquasec.com/wp-content/uploads/2026/11/Java4Shell-blog-banner.jpg" alt="Java4Shell Vulnerability: How Should Security Teams Identify and Reduce Exposure?" class="hs-featured-image" style="width:auto !important; max-width:50%; float:left; margin:0 15px 15px 0;"></a></div>TL;DR: Java4Shell (CVE-2026-114938) is a high severity vulnerability affecting the OpenJDK HotSpot compiler, with a CVSS v3.1 score of 8.1. The published advisory identifies Java 17, 21, 25 and 27 release lines as affected, although exact vulnerable versions vary by distributor. Security teams should identify affected Java installations, prioritize production workloads and apply available security&#160;&mldr;]]></description>
		
		
		
			</item>
	</channel>
</rss>
