Skip to content
Java4Shell: Reported Critical OpenJDK RCE Vulnerability (CVSS 9.2) and Log4Shell Patching Gap

Java4Shell: Reported Critical OpenJDK RCE Vulnerability (CVSS 9.2) and Log4Shell Patching Gap

First seen 21 Nov 2026, 19:46 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 21, 2026 at 19:47 UTC
  • •Java4Shell is reported as an OpenJDK RCE with CVSS 9.2, but the article provides no CVE ID, affected versions, or patch details.
  • •The Java4Shell claims rest on a single Medium post and should be verified against vendor or OpenJDK advisories.
  • •Log4Shell (CVE-2021-44228, CVSS 10.0) remains in CISA KEV, and the article reports about 14% of Log4j downloads still pull vulnerable versions.
  • •Fixed Log4j versions are 2.17.1 for Java 8 and later, 2.12.4 for Java 7, and 2.3.2 for Java 6.
  • •Transitive and shaded Log4j copies inside frameworks and uber-JARs are the main reason patching remains incomplete.

Medium post by RK reports a newly disclosed remote code execution vulnerability named Java4Shell in OpenJDK-based environments, with a CVSS score of 9.2 according to that article. The article states it is not an in the sense of prior exploitation and gives no CVE identifier, patch version, or technical exploitation details. The author claims attackers may have been scanning Java endpoints before disclosure, but this is not independently sourced. A second Medium post by Josiah McCarthy reviews Log4Shell (CVE-2021-44228), a CVSS 10.0 RCE in Apache Log4j 2 versions 2.0-beta9 through 2.14.1, five years after disclosure. That article states that Sonatype reported in December 2025 that 14% of Log4j downloads still pull vulnerable versions, and that CISA's KEV catalog still lists the CVE as actively targeted. It also reports roughly 4,000 organizations remain exposed. Recommended fixed versions are 2.17.1 for Java 8 and later, 2.12.4 for Java 7, and 2.3.2 for Java 6. Both articles are single-author Medium posts with no vendor advisory or official confirmation cited for Java4Shell.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2021-12-09
Log4Shell (CVE-2021-44228) publicly disclosed
Apache Log4j 2 versions 2.0-beta9 through 2.14.1 affected by JNDI lookup injection enabling RCE.
Medium
2021-12-17
CISA issues Emergency Directive ED 22-02
Federal agencies were required to patch or mitigate Log4Shell by December 23, per the article.
Medium
2021-12-22
Joint Advisory AA21-356A published
The advisory documented exploitation by nation-state actors including groups linked to China, Iran, North Korea, and Turkey.
Medium
2025-12
Sonatype reports 14% of Log4j downloads still vulnerable
The article attributes this figure to Sonatype, reported December 2025.
Medium

More articles in this cluster (2)

Following this threat?

Track CISA in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Am I affected by Java4Shell?
The Medium article gives no CVE, affected version range, or vendor advisory, so exposure cannot be determined from these sources. Check OpenJDK and your JDK vendor's advisories directly.
Is Log4Shell still being exploited?
The article states CISA's KEV catalog still lists CVE-2021-44228 as actively targeted. It also reports roughly 4,000 organizations remain exposed.
Which Log4j version should we upgrade to?
The article recommends 2.17.1 for Java 8 and later, 2.12.4 for Java 7, and 2.3.2 for Java 6. Also check shaded and bundled copies inside frameworks and uber-JARs.