· 7 min read · LNX Inc.

Java4Shell puts pre-auth RCE in Jira, Jenkins and Keycloak

Java4Shell hits Java 17 to 27 on AVX-512 servers; Puppet RCE joins CISA's exploited list; Microsoft's agent-framework PyPI package was hijacked.

A systems administrator at a laptop in a server room, a long list of package updates on screen and a rack of servers behind

A bug in the way Java decodes Base64 is the story for Wednesday, November 18, 2026. Researchers at Calif call it Java4Shell, CVE-2026-114938. Oracle and OpenJDK shipped fixes on Tuesday, and CISA published an alert the same day telling everyone to patch. Nobody has reported exploitation in the wild yet. A full exploit is already in a commercial feed, though, so treat this as a this-week job. Any server that runs Jira, Confluence, Jenkins or Keycloak is the place to start.

A Base64 shortcut in the JVM writes past its buffer

Modern x86-64 processors have AVX-512 instructions that let the Java runtime decode Base64 very fast. The HotSpot JVM uses a hand-tuned routine for this, called an intrinsic. Calif's write-up shows that a crafted input makes that routine write past the end of its output buffer on the heap. The input is short: a run of A characters followed by =.

The flaw only fires when three things line up:

  • A Java build in range. Oracle lists Java SE 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3 as affected, plus GraalVM. Calif says OpenJDK is affected from 17.0.6 on. Every OpenJDK-based build is in scope: Temurin, Corretto, Microsoft Build of OpenJDK, Zulu, Red Hat and others.
  • A CPU with AVX-512 VBMI. Calif names Intel Xeon Ice Lake, Sapphire Rapids, Emerald Rapids and Granite Rapids, and AMD Zen 4 or newer. ARM64 is not affected.
  • An application that decodes attacker input. HTTP Basic credentials, tokens and file uploads all pass through the Base64 decoder, often before the login check.

Scores differ. Calif rates it 9.2 under CVSS 4.0. Oracle's advisory rates it 8.1 under CVSS 3.1, with high attack complexity. Rapid7 notes that turning the memory corruption into code execution depends on the application, the JVM build and the memory layout.

Calif got code execution in six products with no login

The list is what makes this urgent for MSPs. In default configurations, Calif reports unauthenticated remote code execution against Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate. With a login, it also reached Apache Kafka, Apache Solr, Elasticsearch, Gerrit and Spinnaker. Calif adds that a Java client that connects to a malicious TLS server can also be hit.

Even without code execution, the bug can take a service down. Blackpoint Cyber, as reported by The Hacker News, crashed a Spring Boot test app with malformed Basic auth headers in about 20 seconds.

The exploit is out of the lab, but only just

DateWhat happened
November 17, 2026OpenJDK publishes its vulnerability advisory; Oracle's November Critical Security Patch Update ships 11 Java SE fixes
November 17, 2026Calif publishes Java4Shell with a trigger-only proof of concept and withholds its working exploits
November 17, 2026CISA publishes Critical Java Vulnerability Requires Immediate Patching
November 17, 2026, 6 PM ESTVulnCheck makes a full RCE exploit available to its paying customers
November 18, 2026No exploitation in the wild reported; the CVE is not in CISA's exploited list
December 15, 2026Oracle's next scheduled security release

As yesterday's briefing noted, the N-central 4EverAble2Shell chain was exploited within hours of its proof of concept going public. Plan on days, not weeks.

Who is exposed

Think about where your clients run Java on recent server hardware:

  • Self-hosted Atlassian, Jenkins and Keycloak. Engineering firms, software shops and anyone with a Jira or Confluence Data Center install. These are the pre-auth cases.
  • Line-of-business apps and appliances that bundle their own Java. Rapid7 says these must be updated through the product vendor, not by patching the system JDK. CISA warns these runtimes often do not show up as separate entries in software inventories.
  • Containers. Images that carry a JRE need a rebuild and redeploy, not just a host update.
  • Cloud VMs. A cloud instance on one of the CPU generations above is just as exposed as a physical server. Check the CPU flags rather than assuming.

Desktops running Java clients are lower priority, but the TLS client path means they are not out of scope.

What to do

  1. Find the runtimes. List every Java process on servers you manage, including the bundled ones. Note the vendor, version and whether the service faces the internet.
  2. Check the CPU. On Linux, Calif's check is that /proc/cpuinfo lists all four of avx512f, avx512bw, avx512vbmi and bmi2. If any is missing, the intrinsic path is not reachable.
  3. Patch internet-facing services first. Rapid7 lists Oracle's fixed builds as 17.0.21.1, 21.0.13.1, 25.0.5.1 and 27.0.1.1, and 8u513-perf. For OpenJDK distributions, take the build your vendor released after November 17 and confirm it names CVE-2026-114938. For Jira, Jenkins and similar products, follow the product vendor's guidance on its bundled runtime.
  4. If you cannot patch today, restart the JVM with -XX:-UseBASE64Intrinsics. Calif and VulnCheck also list -XX:UseAVX=2, which disables AVX-512 entirely; do not use it on ARM, where Java will not start with it. Calif says request buffering at a reverse proxy is not a general fix.
  5. Restart after patching. A running JVM keeps the old code until the process restarts.
  6. Watch for the symptoms. CISA asks admins to look for unexpected JVM crashes, rogue runtimes and suspicious Java processes. A run of crashes on a public Jira or Jenkins server this week deserves a look.

No source has published indicators of compromise yet, so there is no indicator table today.

Also today

Puppet RCE is now on CISA's exploited list. CISA added CVE-2026-115731, a deserialization flaw in Perforce Puppet Enterprise, on November 17, with a federal deadline of December 1. A client holding any CA-signed agent certificate can run code on the Puppet Server. If autosigning approves certificate requests without strong checks, an attacker needs no credentials at all. Neodyme, which found it, warns that a compromised server exposes the CA signing keys. Fixed releases came out November 3: Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13, and Puppet Core 9.1.3 and 8.22.2, as reported by The Hacker News. OpenVox users need openvox-server 9.2.0 or 8.18.0 and openvox-agent 9.3.0 or 8.32.0. If you run Puppet for clients, patch, tighten autosign, and limit which networks can reach the server.

Microsoft's agent-framework package on PyPI was hijacked for 41 minutes. On November 17, someone published versions 1.26.1 and 1.26.2 of agent-framework, the Python package for Microsoft Agent Framework. StepSecurity puts the uploads at 20:35:20 and 21:08:39 UTC; PyPI quarantined the second at 21:16:44 UTC. Both drop a .pth file that runs on every Python start and steals environment variables, credential files, and Azure and GitHub Actions tokens. The last clean release is 1.26.0. Clients building AI tools or Azure automation are the ones to check. Search lockfiles, caches and CI logs for the two versions and for agent_framework_meta.pth or af_runtime_diag.pth. Rebuild affected hosts from clean images and rotate any credential they could read.

A Russian group turned one Workspace breach into a second. Google's Mandiant and Threat Intelligence Group described COLD RELIC, formerly COLDRIVER, on November 17. In the first case, a Super Admin accepted a push-fatigue MFA prompt. The group then enrolled its own passkeys and devices, deleted Alert Center notifications and ran a domain-wide Takeout export. Access survived password resets for months. In the second, it posed as an employee of the first victim to phish Entra ID credentials. Google's advice is phishing-resistant MFA for admins and approval for new authenticators. Its cleanup advice: revoke sessions, OAuth grants, passkeys and backup codes, not just the password. Its detection table lists Passkey enrolled, Customer Takeout Created and Batch Delete Operation Performed as events to alert on.

An Apache Roller flaw is being exploited. The Apache advisory for CVE-2026-129448 (CVSS 9.8) covers an unauthenticated XML-RPC deserialization flaw in Roller 4.0.0 through 6.1.4. It is the same bug as CVE-2026-82384, filed for 6.1.5. Apache says it is actively exploited. Upgrade to 6.1.6. Turning off XML-RPC in the admin screen does not protect older versions.

Sources

Tell us what's in front of you.

A drawing set, a failing switch, an audit deadline, or a hunch that IT costs too much. We'll tell you who picks it up and what it takes.