Skip to content
NewA calmer, faster ZeroHour
Exploit / PoChighExploited in the wild

Attackers probe Java4Shell as vendors rush out OpenJDK advisories

Original title: Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories

SecurityWeekby Eduard Kovacs ()4 min read1
Part of a story covered by 14 sourcesPalo Alto confirms Java4Shell impact; no successful intrusion confirmedMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

CVE-2026-114938 needs an AVX-512 VBMI CPU; sensors have not confirmed a successful intrusion.

Threat actors are scanning and sending exploit-shaped requests for Java4Shell, CVE-2026-114938, a Base64 memory-corruption bug in OpenJDK 17.0.6 and newer on x86-64 CPUs with AVX-512 VBMI. ARM systems are not affected. Calif disclosed it on November 17, when Oracle and OpenJDK shipped patches, and said it achieved unauthenticated RCE against default Jira, Confluence, Jenkins and Keycloak, with a different chain for each product. GreyNoise saw more than 150 matching requests from five IPs and no successful intrusions on its sensors. Cisco, Siemens, Elastic, Red Hat, Atlassian, Keycloak and Jenkins have described impact, with many fixes still pending.

Unconfirmed: GreyNoise, WatchTowr and Previdian report exploit attempts, but none confirm a successful compromise.

Key facts
  • Calif’s public PoC only triggers memory corruption; VulnCheck offers customers a full RCE exploit.
  • Elasticsearch 7.17.3 and later needs credentials for RCE but can be crashed without them.
  • Keycloak fixed vulnerable images in the 26.8.2-3 release.
  • Red Hat says RHEL 8, 9 and 10 and its OpenJDK 17, 21 and 25 builds are affected out of the box.
  • Atlassian cloud customers need take no action; Data Center users can disable AVX-512 until patches.
Security assessment · AI, from the articleExploited in the wild

Impact: Memory corruption that can lead to unauthenticated remote code execution

ProductAffectedFixed in
OpenJDK17.0.6 and newerpatches released November 17
Elasticsearch7.17.3 onward—
Elastic Logstash8.6.2 and later—
Keycloak container images26.8.2-1 and 26.8.2-226.8.2-3
Red Hat RHEL8, 9 and 10—
What to do
  1. 1.Install the November Java updates and restart Jenkins if it runs Java 17, 21 or 25 on AVX-512 VBMI.
  2. 2.Until Data Center patches, disable AVX-512 on affected Atlassian standard installations.
  3. 3.Take affected Siemens Industrial Edge Management instances offline while patches are prepared.
Analyze CVE-2026-114938 with Vani AIImpact, affected versions, exploitation, mitigations and detection

Vulnerabilities mentioned

All
CVEVulnerabilityCVSSEPSSSignalsPublished
CVE-2026-114938
Unauthenticated RCE in Oracle Java SE Compiler
8.1<1%PoC ×23

From the original article

4 min read at securityweek.com

GreyNoise, WatchTowr and Cloudflare report probing and exploit attempts, while Cisco, Elastic, Red Hat and Siemens detail impact. The post Java4Shell Exploitation Attempts Begin as Vendors Rush Out Advisories appeared first on SecurityWeek.

SecurityWeek

By Eduard Kovacs · securityweek.com

Read the full article at SecurityWeek

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.