Java4Shell: Critical Java vulnerability
The critical vulnerability Java4Shell (CVE-2026-114938) allows attackers to execute malicious code on affected systems over the network, in some cases without authentication. Security updates are available. The NCSC recommends that operators immediately check whether their systems are affected and update affected systems.
Java is a technical foundation for many applications. It can also be embedded in software and devices without users being aware of it. The vulnerability affects the Java runtime itself, which runs these programs. When specially crafted data is processed, attackers can read confidential information, manipulate applications or take control of the affected process.
Widely used and business-critical applications affected
Security company Calif has demonstrated the execution of malicious code in several applications:
Without authentication (Pre-Authentication RCE): Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate.
With authenticated access (Post-Authentication RCE): Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Netflix Spinnaker.
These include central authentication services and platforms for software development and deployment. Successful exploitation could therefore also facilitate access to other systems and sensitive information.
The list is not exhaustive. Other Java applications, including banking software and other industry-specific solutions, can also be affected. Operators must clarify their exposure with their software suppliers.
Which systems need to be checked?
The vulnerability affects certain Java versions running on specific, widely used processor types. Whether a system can be exploited also depends on how the application processes data. Consult the relevant vendor’s security advisories to determine whether your systems are affected.
Checks must also cover Java components embedded in applications, devices and containers. Assess internal systems as well as publicly accessible services. According to Calif, attack paths also exist against Java applications that themselves establish connections to a malicious server.
What operators should do now
Prioritise internet-facing applications, central authentication services and business-critical systems.
Identify affected systems: Identify the applications and devices that use Java. Clarify with the vendors or your IT service provider which are affected.
Update your own applications: If you develop and operate Java applications yourself, immediately update the Java version they use.
Update software and devices: Install the security updates provided by the respective vendors for the software and devices you use. If necessary, clarify with the vendor or your IT service provider whether Java also needs to be updated separately. For externally operated services, obtain confirmation that the vulnerability has been addressed.
Verify the update: Restart affected applications and Java processes after updating. Rebuild and redeploy containers where necessary. Verify that running applications actually use the corrected Java version.
If an update is not yet possible: Apply the documented temporary mitigations in coordination with the vendor or your IT service provider. Also restrict unnecessary access.
Check for suspicious activity: Examine affected systems for unusual crashes, unexpected processes and suspicious activity. A security update does not remove an existing compromise.
Technical guidance on affected versions, updates and temporary mitigations is available on the Cyber Security Hub. Temporary mitigations do not replace security updates.
What individuals should do
Promptly install available security updates for your programs and devices using official update functions. Depending on the product, embedded Java components are updated through a software or device update.
Anyone operating their own servers or online services should also follow the recommendations for operators.
NCSC: Technical information on the Cyber Security Hub
Oracle: November 2026 security updates
OpenJDK: Security advisory of 17 November 2026
Calif: Information on Java4Shell
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
