Blog|Articles|November 20, 2026

5 questions to ask your EHR and PM vendors about Java4Shell before Wednesday

Fact checked by: Chris Mazzolini

A critical Java flaw may be sitting inside your practice software. Get these answers from vendors before the office closes for Thanksgiving.

The federal government's top cyber agency spent the week before Thanksgiving telling every organization that runs Java to patch now. The Cybersecurity and Infrastructure Security Agency's alert on the vulnerability, released Nov. 17, warns that a flaw in the Java Virtual Machine's Base64 decoder, tracked as CVE-2026-114938 and nicknamed Java4Shell, can let an attacker crash the software and run code remotely without logging in.

Researchers at the security startup Calif found the bug with help from AI and have already released a general proof-of-concept exploit, according to Dark Reading, which reported a severity score of 9.2 out of 10. Attacks in the wild haven't been reported yet. That gap is the opportunity, and it won't stay open long.

The trouble for small practices is that Java rarely announces itself. It hides inside on-premises practice management servers, lab interfaces, imaging viewers and fax servers, often bundled by the vendor and invisible in a basic software list. A four-day holiday closure is exactly when an unpatched server goes unwatched. If you've already worked through our 11 tech checks before your practice closes for Thanksgiving, this is the follow-up call to make. Here are five questions to put to your vendors before Wednesday.

Affected Java versions at a glance

Here is how Dark Reading breaks down the affected releases. Check Oracle's November advisory and your vendor for the fixed build that applies to your system.

Java version

Status

Java 8

Affected, including the 8u511b33-perf Performance Pack build

Java 11

Not affected

Java 17.0.0 through 17.0.5

Not affected

Java 17.0.6 through 17.0.21

Affected

Java 21 through 21.0.13

Affected

Java 25 through 25.0.5

Affected

Java 27 through 27.0.1

Affected

The 5 vendor questions at a glance

1. Does your product run on Java, and which version?

Ask each vendor whether its product ships with a bundled Java runtime and which build, since CISA warns bundled Java may not show up in a software inventory. Dark Reading lists Java 8, 17.0.6 through 17.0.21, 21 through 21.0.13, 25 through 25.0.5 and 27 through 27.0.1 as affected; Java 11 and 17.0.0 through 17.0.5 are not.

2. When will your tested patch ship, and who installs it?

Oracle addressed the flaw in its November 2026 Critical Security Patch Update, but bundled runtimes should be updated only with vendor approval. Get a written date for each vendor's patched build, who installs it and whether it requires downtime.

3. Which of our systems can be reached from the internet?

CISA says to patch internet-facing systems first, and experts quoted by Dark Reading advised starting with exposed servers running Java 17.0.6 or later and with identity systems. For practices, that usually means patient portals, remote access gateways, remotely reached PM servers and outside lab or hospital interfaces.

4. If you can't patch in time, what will you do instead?

Where a patch isn't ready, CISA lists compensating controls: validate Base64 input at the application boundary, enforce input-size limits and limit unauthenticated access. Vendors should make or approve any temporary fix, and shutting off outside access to an exposed server for the four-day closure is an option.

5. Who is watching your systems over the holiday weekend?

CISA advises monitoring for unexpected Java crashes, rogue runtimes and suspicious Java processes, so confirm who is on call Thursday through Sunday and how they'll be alerted. Dark Reading noted fake exploits and unverified fixes are circulating, so patches should come only from the vendor or Oracle, not from urgent emails or callers posing as vendor support.


Related to this article