A newly disclosed Java vulnerability nicknamed Java4Shell is giving security teams flashbacks to Log4Shell — and for good reason. The flaw sits deep inside the Java runtime that powers many of the business tools Swiss companies run on-premise or through their IT partner: Jira, Jenkins, Confluence, Keycloak, Artifactory and PingFederate among them.
What happened
The US Cybersecurity and Infrastructure Security Agency (CISA) is strongly urging organizations to immediately patch CVE-2026-114938, a critical memory-corruption flaw in the Base64 decoder of the x86-64 HotSpot JVM. A specially crafted Base64 input can crash the Java Virtual Machine and allow unauthenticated remote code execution — meaning an attacker needs no password, no account and no user interaction at all.
Security researchers have gone further, demonstrating pre-authentication RCE directly against Jira, Jenkins and Keycloak. Qualys researchers confirmed the same attack works against default installations of Confluence, Artifactory and PingFederate as well. These are exactly the kind of tools small and mid-sized Swiss businesses rely on for ticketing, code deployment, identity management and document collaboration — often set up years ago and rarely touched since.
The good news: fixes already exist
Oracle moved fast. Fixed builds — Java SE 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1 — shipped on 17 November 2026. Other widely used distributions, including Amazon Corretto, Eclipse Temurin and Azul Zulu, have also released patches. If your Java installation came from any of these sources, an update is already waiting for you.
Why the next few days matter
As of 18 November 2026, there is no public proof-of-concept exploit yet, and the flaw has not been added to CISA's Known Exploited Vulnerabilities catalog. That is the narrow window every business gets after a disclosure like this: the fix is public, but working attack code hasn't leaked yet. Once it does — and history shows this tends to happen within days for flaws this severe — mass scanning and automated exploitation typically follow within hours, not weeks.
This pattern is becoming the new normal. Just this week, security teams have also tracked fully automated exploit pipelines that turn freshly released patches into working attacks with no human involved. Every disclosure like Java4Shell is now effectively a countdown.
What to do today
- Inventory your Java-based systems. Check every server running Jira, Jenkins, Confluence, Keycloak, Artifactory, PingFederate — and anything else built on Java that your business or IT provider manages.
- Identify your Java version and vendor. Confirm whether you run Oracle Java, Corretto, Temurin or Zulu, and check the version number against the fixed builds above.
- Patch immediately, starting with internet-facing systems. Anything reachable from outside your network — a Jenkins build server, a Confluence wiki, a Keycloak login page — should be prioritized first, since no login is needed to exploit this flaw.
- Don't forget systems managed by your IT partner. If an outsourced provider runs these tools for you, ask directly, today, whether they have patched or scheduled patching.
- Restart services after patching. Java updates typically require a service or server restart to take effect — a patch sitting unapplied on disk doesn't protect anything.
The bigger picture
Java4Shell is the latest reminder that critical infrastructure software — the runtime underneath the tools, not the tools themselves — can be the weakest link. Most businesses watch their applications closely but rarely check what version of Java, PHP or OpenSSL is quietly running underneath. That is exactly where attackers are looking now.
This is the kind of vulnerability that benefits from someone watching patch advisories daily, not once a quarter. If keeping track of every CISA alert and vendor patch note alongside running your business sounds exhausting, that is precisely where an IT partner earns its keep. Flitz.ai, provided by The Mejlerö Company GmbH, helps Swiss SMEs in Obwalden, Nidwalden, Lucerne and Zurich with practical, ongoing IT support — including keeping an eye on exactly this kind of critical patch — alongside automating the routine parts of running a business. A free network analysis and a free one-hour consultation are a good way to find out where your own exposure sits.
We'll keep watching this space and report back with the next critical fix you need to know about.