Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/theori-io/java4shell-runtime-patch-cve-2026-114938
Defensive ToolsContainer SecurityVulnerability AnalysisExploitationDevSecOpsIncident ResponseBinary Exploitation
GitHub
Share
theori-io/java4shell-runtime-patch-cve-2026-114938

java4shell-runtime-patch-CVE-2026-114938

Runtime JVMTI agent that disables the vulnerable Base64 decode intrinsic in running JVMs via compiler directives and class retransformation, patching CVE-2026-114938 without restart.

View Repository
1862 days agoNot yet reviewed

CVE-2026-114938 Runtime Patch (Temporary Patch Provided by Xint)

Attaches an agent to a running JVM so that the vulnerable intrinsic (_base64_decodeBlock, the x86_64 AVX-512 VBMI Base64 decode stub) is no longer executed. No JVM memory is written directly. It uses only supported interfaces: compiler directives and class retransformation.

The change lives in memory only and is lost on restart. Add -XX:-UseBASE64Intrinsics to the JVM startup options in your next deployment.

Usage

0) One-liner (curl | sh)

curl -fsSL https://files.xint.io/java4shell | sh                        # check, then apply after typing "yes"
curl -fsSL https://files.xint.io/java4shell | sh -s -- --dry-run        # check only
curl -fsSL https://files.xint.io/java4shell | sh -s -- --yes [PID ...]  # apply without prompting (automation)
# To pin the installer download itself as well:
curl -fsSL --pinnedpubkey 'sha256//cPNKVMMSBKRsqcDzoa/6g1kBw43KpwPCZYPU38YC1Ig=;sha256//QYVBGSU2fPejSOSSjdZ9qAChBxEHY/8AcSb9/SSeYPQ=' https://files.xint.io/java4shell | sh
  • java4shell downloads the jar and apply.sh with the files.xint.io leaf public key (SPKI) pinned (curl --pinnedpubkey, both the ECDSA and the RSA certificate). It then verifies their SHA-256. If any check fails, nothing is executed.
  • Server layout:
    • https://files.xint.io/java4shell (installer)
    • https://files.xint.io/java4shell.d/CVE-2026-114938.jar
    • https://files.xint.io/java4shell.d/apply.sh
  • If you rebuild the jar or apply.sh, update JAR_SHA256 / APPLY_SHA256 in java4shell.
  • Pins must be maintained. The current certificates are Cloudflare-managed and valid for 90 days (expire 2027-01-24). If the key changes on renewal, the pins break and installs stop with "pin mismatch" (fail closed). After a renewal, recompute the pins and update PINS. For long-term use, prefer a certificate with a stable key, such as a Cloudflare custom certificate.
    openssl s_client -connect files.xint.io:443 -servername files.xint.io </dev/null 2>/dev/null \
      | openssl x509 -pubkey -noout | openssl pkey -pubin -outform der | openssl dgst -sha256 -binary | base64
    # RSA certificate: add  -tls1_2 -cipher ECDHE-RSA-AES128-GCM-SHA256  to s_client
    

Where to run it

Requirements:

  • jcmd (a JDK) is available where you run it.
  • The target JVM processes are visible from there (same host or same container).
  • You are root, or the same user as the target JVM.
EnvironmentWhereCommand
VM / bare metal, Java started directlyOn the server (JDK installed)curl -fsSL https://files.xint.io/java4shell | sudo sh
Docker, app image contains a JDKInside the app containerdocker exec -it <ctr> sh -c 'curl -fsSL https://files.xint.io/java4shell | sh'
Docker, JRE-only image or no JDK on the hostPrivileged JDK helper container in the host PID namespace (covers every container JVM on the host)docker run --rm -it --privileged --pid=host eclipse-temurin:21-jdk sh -c 'curl -fsSL https://files.xint.io/java4shell | sh'
Host has a JDKOn the host as root (container JVMs are visible too)curl -fsSL https://files.xint.io/java4shell | sudo sh
Kubernetes, per podkubectl exec (image contains a JDK)kubectl exec -it <pod> -- sh -c 'curl -fsSL https://files.xint.io/java4shell | sh'
Kubernetes, per nodeNode debug pod (works for JRE images)kubectl debug node/<node> -it --profile=sysadmin --image=eclipse-temurin:21-jdk -- sh -c 'curl -fsSL https://files.xint.io/java4shell | sh'
  • The helper JDK version does not need to match the target JVM version. A JDK 21 helper patching a JDK 17 JVM and a JRE 21 JVM was verified.
  • -it is needed for the interactive "yes" prompt. For automation, append sh -s -- --yes.
  • Air-gapped environments: copy the zip and run ./apply.sh --dry-run, then ./apply.sh.
  • The target container's /tmp must be writable (the JVM attach mechanism uses it).

1) On a server or inside a container: apply.sh

./apply.sh --dry-run          # check all running JVMs (changes nothing)
./apply.sh                    # apply to all running JVMs (only exposed JVMs are changed; asks "yes")
./apply.sh 1234 5678          # specific PIDs only
./apply.sh --force 1234       # apply regardless of the checks
./apply.sh --yes              # no confirmation prompt (automation)
  • Without PIDs, it finds every process running as */bin/java (jcmd itself is excluded).
  • For each PID it prints the check result, the apply result, and STATUS: patched / not patched.
  • Requirements: jcmd on PATH, and either root or the same user as the target JVM.
  • Run as root on the host, it also patches JVMs in other containers (the jar is copied through /proc/PID/root/tmp). The host then needs a JDK as well.

2) Kubernetes, per pod

NS=default; POD=my-app-xxxx; C=app      # container name
kubectl cp CVE-2026-114938.jar $NS/$POD:/tmp/CVE-2026-114938.jar -c $C
kubectl cp apply.sh            $NS/$POD:/tmp/apply.sh            -c $C
kubectl exec -n $NS $POD -c $C -- bash /tmp/apply.sh --dry-run
kubectl exec -n $NS $POD -c $C -- bash /tmp/apply.sh --yes

Multiple pods at once:

for p in $(kubectl get pods -n $NS -l app=my-app -o name); do
  kubectl cp CVE-2026-114938.jar $NS/${p#pod/}:/tmp/CVE-2026-114938.jar -c $C
  kubectl cp apply.sh            $NS/${p#pod/}:/tmp/apply.sh            -c $C
  kubectl exec -n $NS ${p#pod/} -c $C -- bash /tmp/apply.sh --yes
done

2-1) Kubernetes, per node (recommended for JRE images and many pods)

No jcmd is needed in the app images, and every JVM on the node is handled at once.

# Start a node debug pod (hostPID, privileged) with a JDK image
kubectl debug node/<node> -it --profile=sysadmin --image=eclipse-temurin:21-jdk -- bash
# From another terminal, copy the package (debug pod name is printed by the command above)
kubectl cp CVE-2026-114938 <debug-pod>:/tmp/CVE-2026-114938
# Inside the debug pod
bash /tmp/CVE-2026-114938/apply.sh --dry-run      # check every JVM on the node
bash /tmp/CVE-2026-114938/apply.sh                # apply after confirmation ("yes")

3) Docker

docker cp CVE-2026-114938.jar <ctr>:/tmp/ && docker cp apply.sh <ctr>:/tmp/
docker exec -it <ctr> bash /tmp/apply.sh

4) jcmd directly

jcmd <pid> JVMTI.agent_load /path/CVE-2026-114938.jar            # apply
jcmd <pid> JVMTI.agent_load /path/CVE-2026-114938.jar dry-run    # check only
jcmd <pid> JVMTI.agent_load /path/CVE-2026-114938.jar force      # apply regardless of checks

Output goes to the target JVM's stderr and to <jar dir>/CVE-2026-114938-<pid>.log. To verify: jcmd <pid> Compiler.directives_print | grep 'Base64$Decoder.decode0'

Checks

If any of the following is true, the agent prints not exposed and exits without changing anything. force applies anyway.

  • The JDK is older than 17.0.6, or the platform is not x86_64.
  • The CPU features detected by the JVM lack avx512_vbmi or avx512bw. This also covers AVX-512 lowered via UseAVX.
  • UseBASE64Intrinsics=false, i.e. already disabled at startup.

Running it again on the same JVM skips adding the directive (already present) and only redoes the deoptimization.

How it works

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    938
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    556
  • 3

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    352
  • 4

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    343
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    336
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    291

Explore all tools

Browse our collection of tools

View all tools →