- Plain-language security guides for Central Florida businesses/
- News/
- Java4Shell: What to Ask Whoever Runs Your Business Software/
Java4Shell: What to Ask Whoever Runs Your Business Software

Table of Contents
What happened #
Oracle’s security notice lists the flaw and the fixed versions. It rates the flaw high and calls it difficult to pull off. The research firm Calif, which found it, rates it critical. Calif says an outsider with no login could take control of the computer running some popular tools by sending it a specially made piece of text. It says it did this in its own test setups, with standard settings, against Jira, Confluence, Jenkins and other well-known products.
Calif says no single attack works everywhere, because each product needs its own. It has published a short test program that shows the flaw exists, and is holding back its attack code for now.
The flaw only matters in some setups. Red Hat says the software must run on Java 17 or newer, on a computer with a newer Intel or AMD server processor. Older versions of Java and computers with ARM processors are not affected. Whether that describes your setup is something only the person who runs the server can check.
What this means for a business owner #
Updating the program on top will not necessarily fix it. The flaw is in Java itself. Red Hat says that for products that come with their own copy of Java, the fix arrives through the maker of that product. CISA, the US cyber agency, says these private copies, inside software packages or devices, may not show up in a list of what is installed.
On a hosted or cloud version of a tool, the provider does the update. Your job is to ask, and to get a clear answer.
On a server your business or IT person runs, they have to install a fixed version of Java and restart each program that uses it. The old version keeps running until the restart. Qualys, a security company, also warns against skipping the update because the processor looks safe. A computer that is unaffected today can end up on an affected one after a move to newer hardware or a larger cloud server.
Fixes are arriving at different speeds. Amazon’s security page shows its fixed versions came out on November 17. The Eclipse Temurin project, a widely used free build of Java, said fixed builds were being released as testing finished. Red Hat said it was rushing its own. As of November 18, a provider’s fix may still be on its way.
Red Hat and Eclipse Temurin both describe a temporary setting that turns off the part of Java that has the flaw. It can slow some work and is not a fix, so it is a decision for your IT person.
What we do not know #
Whether anyone is being attacked. ThreatDefence, a security monitoring firm, wrote on November 18 that no attacks had been reported and that the flaw was not on CISA’s list of flaws being used in attacks. Calif’s test program is public, and Calif says details leaked before the fix came out, so that could change.
How many businesses are affected. We found no count, and the severity ratings differ, as above.
Whether your own systems are affected. That depends on the Java version, the processor and the program. Your IT person or vendor can tell you.
Five questions to ask this week #
- Do any of our systems run on Java, and who keeps that Java up to date? Tools such as Jira, Confluence and Jenkins, a company login system, or a search or data server often do.
- Has Java been updated to a fixed version from our provider since November 17, and was each program restarted afterward? Please answer in writing.
- Do any of our programs carry their own private copy of Java, and has each maker said when its update ships?
- If an update is not ready for something, can the temporary setting be used until it is, and can the tool be limited to people who are logged in or taken off the open internet? CISA suggests limiting access for people who are not logged in. This lowers the risk but does not fix the flaw.
- After the update, did anyone look for signs of a break-in? CISA lists programs that crash or restart for no clear reason, Java starting programs it never started before, and copies of Java nobody can account for. An update closes the flaw. It does not remove anything planted earlier.
These questions will not prevent an attack. The update is the fix.
If you think a system was already broken into #
Call your IT person right away. ThreatDefence advises keeping the crash files and logs before restarting anything, then updating Java and changing the passwords and keys the program could reach if there is evidence an attacker ran code.
Take this to your next IT meeting #
Send the five questions today and ask for written answers. If you are not sure which of your tools run on Java, that is the first thing to find out.
At SOC-Lite, a named analyst reviews your alerts, calls you when one is real, works with your IT person or MSP on the fix, and keeps the evidence. A visibility check is free, it takes 20 minutes, and you talk to us by phone or at your office. Book a visibility check
Updates #
2026-11-18: First published, based on the sources below as of this date.
Sources #
- Oracle, Critical Security Patch Update, November 2026: release date, the severity rating and the note that the flaw is difficult to exploit.
- Calif, Java4Shell: Write once, RCE everywhere: what an outsider could do, the products tested, no single attack that works everywhere, the published test program, the withheld attack code, the leak before the fix.
- Red Hat, RHSB-2026-018: Java 17 or newer, the processor condition, products with their own Java, the temporary setting, fixes being rushed.
- CISA, Critical Java Vulnerability Requires Immediate Patching: private copies of Java missing from inventories, limiting access, what to watch for.
- Eclipse Temurin (Adoptium), guidance for Java4Shell: fixed builds being released, the temporary setting.
- Amazon Linux Security Center, CVE-2026-114938: fixed versions released November 17.
- Qualys, How to Find, Mitigate, and Patch the Critical Java4Shell Flaw: restart after updating, the processor point, Oracle’s score.
- ThreatDefence, Java4Shell fixes and hunting: no reported attacks and no listing as of November 18, what to keep after a suspected break-in.