# Java4Shell: OpenJDK HotSpot Base64 decoder memory corruption (CVE-2026-114938)

Pack 1.0.0, 17 Nov 2026. CybaVerse threat hunt. Hubfs folder: `openjdk-cve-2026-114938-pack-v1`.

Read-only checker (bash and PowerShell), six KQL hunts, six Sigma rules. Every hunt is OUR PATTERN: neither OpenJDK
nor Oracle publishes indicators of compromise.

## At a glance

| Item | Value | Source |
|---|---|---|
| CVE | CVE-2026-114938, HotSpot compiler (OpenJDK component `hotspot/compiler`; Oracle component "Compiler") | OpenJDK advisory, Oracle CSPU |
| Weakness | CWE-122 Heap-based Buffer Overflow | CISA ADP on the CVE record |
| Vendor score | CVSS 3.1 **8.1 High**, `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H` (high attack complexity, no authentication) | Oracle (the CNA) on cve.org, the OpenJDK advisory and the Oracle CSPU |
| Researchers' score | CVSS 4.0 9.2, rated critical by the reporting security researchers | NEWS: BleepingComputer |
| Our framing | **Critical by impact (our framing).** The vendor and CNA score is 8.1 High, below 9.0, so this pack does not call it Critical | OUR ADVICE |
| Exploited | No exploitation reported. CISA ADP SSVC: Exploitation none, Automatable no, Technical Impact total | cve.org (CISA ADP) |
| CISA KEV | Not listed in catalogue 2026.11.17 (released 17 Nov 2026 17:53 UTC, 17:53 London time) | CISA KEV feed |
| NVD | Published 17 Nov 2026 22:18 UTC, status Received, Oracle CVSS 3.1 8.1 only | NVD |
| Fix | Oracle JDK and OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 (17 Nov 2026), Oracle Java SE 8u513-perf, and vendor builds below | Oracle JDK release notes, vendor pages |
| Public PoC | BleepingComputer reports a public memory-corruption proof of concept; the app-specific exploits are not public. This pack does not link it | NEWS: BleepingComputer |

**Vendor advice (credited to Oracle and OpenJDK):** OpenJDK: "We recommend that you upgrade as soon as possible."
Oracle's Java SE release notes for each 17 Nov build: "This release contains fixes for security vulnerabilities
described in the Oracle Critical Patch Update."

**OUR ADVICE (CybaVerse, not from Oracle):** update every Java 17, 21, 25 and 27 runtime now, internet-facing app
servers first (Jira, Confluence, Jenkins, Keycloak, Artifactory, PingFederate), including JREs bundled inside
products. Where you cannot update today, add `-XX:-UseBASE64Intrinsics` (see "Workaround") and keep the apps behind
SSO or VPN. Patch now regardless of KEV status.

## What each source says about affected and fixed builds

There is no conflict between OpenJDK and Oracle: **both list 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3 and 27.0.1.0.3 as
AFFECTED.** The flag's "fixed after" wording was right about direction, and a later room correction that called
these the fixed builds was wrong (since withdrawn). The fixed builds are the `.1` updates released 17 Nov 2026.

- **OpenJDK advisory 2026/11/17:** "The following vulnerabilities in OpenJDK source code were fixed in this release.
  The affected versions are 27.0.1.0.3, 25.0.5.0.3, 21.0.13.0.3, 17.0.21.0.3, 11.0.33, 8u512, and earlier." That
  sentence covers the whole release (ten CVEs). The per-CVE risk matrix marks CVE-2026-114938 under 17, 21, 25 and
  27 only, not under 8 or 11. So 8 and 11 are out of scope for this CVE (but take their 17 Nov updates for the other
  CVEs).
- **Oracle CSPU Java SE risk matrix and the CVE record (Oracle is the CNA):** "Supported versions that are affected
  are Oracle Java SE: 8u511b33-perf, 17.0.21.0.3, 21.0.13.0.3, 25.0.5.0.3, 27.0.1.0.3; Oracle GraalVM for JDK:
  17.0.21.0.3 and 21.0.13.0.3; Oracle GraalVM Enterprise Edition: 21.3.20.0.3." The record lists every one of these
  with status "affected".
- **Oracle JDK release notes, 17 Nov 2026:** "The full version string for this update release is 17.0.21.1+4",
  and likewise 21.0.13.1+4, 25.0.5.1+4 and 27.0.1.1+4. Each says "This release contains fixes for security
  vulnerabilities described in the Oracle Critical Patch Update." They do not name the CVE.
- **Oracle JDK 8u513-perf release notes:** "The full version string for this update release is 1.8.0_513-perf-b4".
  JDK 8u513 (non-perf) is 1.8.0_513-b04.
- **Oracle GraalVM release notes:** "Oracle GraalVM for JDK 21.0.13.1 (2026-11-17) This is the November 2026 Oracle
  Critical Security Patch Update (CSPU) for Oracle GraalVM for JDK 21. Updated the Oracle JDK release on which Oracle
  GraalVM is built to 21.0.13.1+4." For JDK 17 and for Enterprise Edition the notes conflict, see below.
- **Upstream OpenJDK tags** (as imported by Amazon Corretto): jdk-17.0.21.1+2, jdk-21.0.13.1+2, jdk-25.0.5.1+2 and
  jdk-27.0.1.1+4. Upstream and Oracle builds share the version number; the build number after `+` differs.

**Conflict, stated plainly [REVIEW]:** Oracle's GraalVM release notes say "Oracle GraalVM for JDK 17.0.21.1
(2026-11-17) This is the November 2026 Oracle Critical Security Patch Update (CSPU) for Oracle GraalVM for JDK 17.
Updated the Oracle JDK release on which Oracle GraalVM is built to 17.0.20.1+4." and that Enterprise Edition
21.3.20.1 is built on "17.0.20.1+4 for Java 17-based Oracle GraalVM Enterprise Edition". 17.0.20.1 is below the
Oracle JDK 17 fix (17.0.21.1+4) and below a build Oracle lists as affected. This may be a documentation error, but
until Oracle confirms, the checker reports Oracle GraalVM for JDK 17 at 17.0.21.1 or 17.0.20.1 as REVIEW (exit 3),
never as fixed.

### Affected and fixed table

| Product and line | Affected (per source) | Fixed build | Status of fix |
|---|---|---|---|
| OpenJDK / Oracle JDK 17 | 17.0.21.0.3 and earlier (OpenJDK, Oracle) | 17.0.21.1 (Oracle 17.0.21.1+4) | Shipped 17 Nov 2026 |
| OpenJDK / Oracle JDK 21 | 21.0.13.0.3 and earlier | 21.0.13.1 (Oracle 21.0.13.1+4) | Shipped 17 Nov 2026 |
| OpenJDK / Oracle JDK 25 | 25.0.5.0.3 and earlier | 25.0.5.1 (Oracle 25.0.5.1+4) | Shipped 17 Nov 2026 |
| OpenJDK / Oracle JDK 27 | 27.0.1.0.3 and earlier | 27.0.1.1 (Oracle 27.0.1.1+4) | Shipped 17 Nov 2026 |
| Oracle Java SE 8 Enterprise Performance Pack | 8u511b33-perf (Oracle) | 8u513-perf (1.8.0_513-perf-b4) | Shipped 17 Nov 2026 |
| OpenJDK / Oracle JDK 8 (non-perf) and 11 | Not marked for this CVE | n/a (8u513, 11.0.33.1 fix other CVEs) | Out of scope |
| Oracle GraalVM for JDK 21 | 21.0.13.0.3 | 21.0.13.1 (built on 21.0.13.1+4) | Shipped 17 Nov 2026 |
| Oracle GraalVM for JDK 17 | 17.0.21.0.3 | 17.0.21.1 named as the CSPU | [REVIEW] notes say built on 17.0.20.1+4 |
| Oracle GraalVM Enterprise Edition 21.3 | 21.3.20.0.3 | 21.3.20.1 named as the CSPU | [REVIEW] Java 17 base given as 17.0.20.1+4 |
| Amazon Corretto | Earlier builds, for example 17.0.21.0.11, 21.0.13.0.11 | 17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4 | Shipped; each change log lists CVE-2026-114938 (CVSS 8.1, hotspot/compiler) |
| Azul Zulu | Azul lists Zulu 27, 25, 21, 17 as affected | November 2026 CSPU: JDK 27.0.1.1, 25.0.5.1, 21.0.13.1, 17.0.21.1; CPU-line SA builds 25.0.4.1.201, 21.0.12.1.201, 17.0.20.1.201 | Shipped; release notes list CVE-2026-114938 |
| Eclipse Temurin | Per news | None yet: the Adoptium API lists jdk-17.0.21+9, jdk-21.0.13+9, jdk-25.0.5+8 and jdk-27.0.1.0.2+1 as latest | Not shipped when checked [UNVERIFIED later] |
| Microsoft Build of OpenJDK | Per news | None listed: release notes "Last updated on 2026-11-04" | Not shipped when checked [UNVERIFIED later] |
| Red Hat build of OpenJDK | Per news | No Red Hat CVE page found (HTTP 404) | Not confirmed [UNVERIFIED] |
| Apps with bundled JREs (Jira, Confluence, Jenkins, Keycloak, Artifactory, PingFederate) | Per news | Vendor bundle updates | Check each vendor [UNVERIFIED] |

BleepingComputer reports "Java4Shell affects OpenJDK 17.0.6 and later". OpenJDK and Oracle give no lower bound
("and earlier"), so this pack treats every 17 build below 17.0.21.1 as affected and the checker notes the news claim
for builds below 17.0.6.

## CPU precondition

- NEWS (BleepingComputer): the flaw "only affects a hardware-accelerated decoding function used on certain x86-64
  processors that support AVX-512 instructions" and needs "supported x86-64 processors with AVX-512 VBMI
  capabilities". OpenJDK and Oracle do not state a CPU condition.
- Checked against the HotSpot source (jdk17u, jdk21u and jdk25u update repositories, read 17 Nov 2026): the x86-64
  Base64 decode stub (`generate_base64_decodeBlock` in `src/hotspot/cpu/x86/stubGenerator_x86_64.cpp`) takes its
  AVX-512 path only when `VM_Version::supports_avx512_vbmi() && VM_Version::supports_avx512bw()`. That code is x86
  only. OUR ASSUMPTION: ARM64 and other non-x86 JVMs do not reach it.
- Check on Linux: `grep -o -w -m1 avx512vbmi /proc/cpuinfo` (no output means absent), or let the checker read
  `/proc/cpuinfo`. On Windows there is no built-in command we have verified for this flag [UNVERIFIED]: save a flag
  list from a hardware inventory tool you trust and pass it with `-CpuFlagsFile`.
- A VM guest sees the flags its hypervisor exposes, and a JVM moved to a newer host can gain AVX-512 VBMI. The
  checker therefore reports "AFFECTED, CPU PRECONDITION ABSENT" (exit 6), never "not affected", for an affected
  version on a CPU without the flag.

## Workaround: exact flag semantics

Both flags come from BleepingComputer (credited there to the reporting security researchers). We checked them in
the HotSpot source and in Oracle's `java` manual. They are temporary; update anyway.

| Flag | What the source shows | Effect on this flaw | Cost |
|---|---|---|---|
| `-XX:-UseBASE64Intrinsics` | `product(bool, UseBASE64Intrinsics, false, "Use intrinsics for java.util.Base64")` in `globals.hpp` (17, 21, 25 and mainline). A product flag, not diagnostic or experimental. On x86 the VM turns it on when it is left at default (JDK 17: `UseAVX > 2` with avx512vl and avx512bw; JDK 21 and 25: `UseAVX >= 2`). An explicit `-` keeps it off | Turns off all java.util.Base64 intrinsics, so the AVX-512 decode stub is never used | Base64 falls back to Java code (also loses the AVX2 path on 21 and later) |
| `-XX:UseAVX=2` (or 0 or 1) | `product(int, UseAVX, 3, "Highest supported AVX instructions set on x86/x64")` in `globals_x86.hpp`. With `UseAVX < 3` the VM clears its AVX-512 feature bits, including `CPU_AVX512_VBMI` (`vm_version_x86.cpp`) | `supports_avx512_vbmi()` is then false, so the AVX-512 decode path is not taken | All AVX-512 code paths in the JVM are lost, a wider performance cost |

- **Do you need `-XX:+UnlockDiagnosticVMOptions`?** The HotSpot source says no: `UseBASE64Intrinsics` is declared
  `product`, unlike neighbours such as `UsePoly1305Intrinsics`, which are `DIAGNOSTIC`. Oracle's JDK 21 `java`
  manual, however, says under `-XX:+UseBASE64Intrinsics`: "Flags that control intrinsics now require the option
  -XX:+UnlockDiagnosticVMOptions." OUR ADVICE: put `-XX:+UnlockDiagnosticVMOptions` before the flag. It is harmless
  and satisfies both readings. A JVM that rejects a flag refuses to start, so a running JVM that shows the flag on
  its command line has accepted it.
- **Order matters (OUR ASSUMPTION, standard HotSpot behaviour):** the last setting of a flag wins. A later
  `-XX:+UseBASE64Intrinsics` or `-XX:UseAVX=3` undoes the workaround. The checker reads settings in order.
- **Where to set it:** the app's JVM options file or service definition. `JAVA_TOOL_OPTIONS` also works but is
  read by every JVM on the host. Flags in `@argfiles`, `-XX:Flags=` or `-XX:VMOptionsFile=` files are not read by
  the checker (it warns).
- Confirm on a running JVM with `jcmd <pid> VM.flags -all` (OUR ADVICE; the checker does not run it).

## Reported impact (NEWS, not verified)

BleepingComputer, citing the reporting security researchers: unauthenticated RCE in default configurations of
Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins and PingFederate; authenticated RCE in
Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit and Spinnaker; exploitation in sample Apache Struts and Spring
Boot applications. "Java4Shell does not have a universal exploit, and attackers must find an application-dependent way
to deliver malicious Base64 data to the vulnerable decoder to achieve code execution." We have not verified any of these app claims. Oracle's
risk matrix note says the flaw "can only be exploited by supplying data to APIs in the specified Component without
using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service."

## Hunts (all OUR PATTERN)

`kql/java4shell-cve-2026-114938-hunting.kql` (Microsoft Defender XDR and Sentinel) and `sigma/`:

| Hunt | KQL | Sigma | ATT&CK |
|---|---|---|---|
| Java runtime inventory, below the fixed build per line | Q1 (DeviceTvmSoftwareInventory) | none (no Sigma log source for inventory) | T1190 Exploit Public-Facing Application |
| Devices Defender maps to the CVE (empty until Microsoft adds it) [UNVERIFIED] | Q2 (DeviceTvmSoftwareVulnerabilities) | none | T1190 Exploit Public-Facing Application |
| JVM crashes: new `hs_err_pid<pid>.log` | Q3 | `file_event_win_jvm_hs_err_log.yml`, `file_event_lnx_jvm_hs_err_log.yml` | T1499.004 Endpoint Denial of Service: Application or System Exploitation |
| Java app-server process starting sh, bash, dash, zsh, cmd or PowerShell | Q4 | `proc_creation_win_java_app_child_shell.yml`, `proc_creation_lnx_java_app_child_shell.yml` | T1059.001 Command and Scripting Interpreter: PowerShell; T1059.003 Command and Scripting Interpreter: Windows Command Shell; T1059.004 Command and Scripting Interpreter: Unix Shell |
| New public outbound destinations from app-server JVMs | Q5 | `net_connection_win_java_app_outbound.yml` (review list, no baseline) | T1071.001 Application Layer Protocol: Web Protocols |
| Long Base64 runs in web and API logs [UNVERIFIED fields] | Q6 | `webserver_long_base64_request.yml` | T1190 Exploit Public-Facing Application |

- App markers (atlassian, jira, confluence, jenkins, keycloak, artifactory, jfrog, pingfederate) and install-folder
  markers are OUR ASSUMPTION [UNVERIFIED]; adjust them to your hosts.
- The default fatal error log name and location come from Oracle's troubleshooting guide: without `-XX:ErrorFile`
  the default name is `hs_err_pid<pid>.log` (pid is the process ID), written to the working directory of the
  process, or to the temporary directory when that fails.
- Q6: a generic Base64 run of 256 or more characters, plus an `AllAPad` flag for a run of 64 or more "A" characters
  followed by "=". That flag is OUR heuristic, derived from the trigger shape BleepingComputer reports; this pack does
  not reproduce any exploit string. Authorization headers and request bodies are often not logged, so a quiet result
  proves nothing.
- Sigma conversions for five Kusto pipelines are in `sigma/converted/`. Documented failures: the webserver rule has
  no table in the Microsoft XDR, Microsoft 365 Defender and Sentinel ASIM pipelines, and the Azure Monitor pipeline
  supports none of the Defender-style categories used; see the files.

## Checker

`scripts/check-java4shell.sh` (bash) and `scripts/Check-Java4Shell.ps1` (PowerShell 7) give identical output and
exit codes. They open no sockets, write no files and never run `java`. They read only the files you name, plus
`/proc/cpuinfo` on Linux when no CPU option is given. They print version numbers, vendor names and the flags they
check. `--show-args` prints the JVM arguments with values of `-D` properties and `--options` whose names contain
pass, pwd, secret, token, credential, apikey, api key, private key or auth replaced by `[REDACTED]`, and with the
user and password part of URLs removed.

```
java -version > java-version.txt 2>&1                             # run on the host yourself; the checker never runs java
cp /proc/<pid>/cmdline jvm-args.txt                               # NUL separated; or pass /proc/<pid>/cmdline directly
bash check-java4shell.sh --java-version-file java-version.txt --jvm-args-file jvm-args.txt
bash check-java4shell.sh --java-home "$JAVA_HOME" --cpu-flags-file saved-cpuinfo.txt
pwsh Check-Java4Shell.ps1 -JavaVersionFile java-version.txt -CpuFlagsFile cpu-flags.txt -JvmArgsFile jvm-args.txt
```

Per release line it reports FIXED (at or above 17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1), AFFECTED, NOT AFFECTED
(8 non-perf and 11), REVIEW (Oracle GraalVM for JDK 17, see the conflict above) or UNKNOWN (other lines). It
recognises the Oracle 8 perf build (affected below 1.8.0_513-perf) and the Azul Zulu CPU-line builds Azul lists as
fixed. AVX-512 VBMI is PRESENT, ABSENT or UNKNOWN. The workaround is EFFECTIVE, NONE SEEN or UNKNOWN, using the last
setting of each flag.

| Exit | Meaning |
|---|---|
| 0 | NOT AFFECTED: fixed build, or a line OpenJDK and Oracle do not list for this CVE |
| 1 | not used (reserved for unexpected runtime errors) |
| 2 | AFFECTED: affected version, no workaround seen, AVX-512 VBMI present or unknown |
| 3 | UNKNOWN: no usable version, an uncovered line, or REVIEW (sources disagree) |
| 4 | MITIGATED: affected version with an effective workaround flag (temporary) |
| 5 | USAGE OR READ ERROR |
| 6 | AFFECTED, CPU PRECONDITION ABSENT: affected version, no workaround seen, AVX-512 VBMI absent |

Limits: vendor version strings vary; the checker reads the quoted `version "..."` value and the `(build ...)`
values [UNVERIFIED for every vendor]. Bundled JREs need their own `java -version` or `release` file. Environment
variables not in the saved text are not seen.

## Caveats

- The KQL in this pack has NOT been run against a live tenant. It parses cleanly against modelled schemas only.
- Not in CISA KEV (catalogue 2026.11.17). BOD 26-04 due dates apply to US federal agencies only and are N/A unless
  CISA adds the CVE. Patch now regardless of KEV status.
- No exploitation is claimed. CISA ADP records Exploitation "none".
- The CPU precondition, the 17.0.6 lower bound, the app impact lists, the 9.2 score and both workaround flags come
  from BleepingComputer, not from the OpenJDK or Oracle advisories. We checked the flags and the CPU test in the
  HotSpot source.
- OUR ASSUMPTION: the last setting of a JVM flag wins; non-x86 JVMs do not reach the vulnerable stub.
- Downstream fix status (Temurin, Microsoft, Red Hat) was read on 17 Nov 2026 around 23:40 London time and will
  change.

## Corrections to the original flag

1. "Fixed after 17.0.21.0.3, ..." is right in direction: those builds are the last affected (OpenJDK: "The affected
   versions are ..."; Oracle: "Supported versions that are affected are ..."). The fixed builds are 17.0.21.1,
   21.0.13.1, 25.0.5.1 and 27.0.1.1 (Oracle +4). The room correction calling the `.0.3` builds fixed was wrong.
2. Oracle also lists Oracle Java SE 8u511b33-perf (fixed in 8u513-perf), Oracle GraalVM for JDK 17.0.21.0.3 and
   21.0.13.0.3, and GraalVM Enterprise Edition 21.3.20.0.3. OpenJDK 8 and 11 are not marked for this CVE; the
   advisory's "11.0.33, 8u512" applies to the release as a whole.
3. GraalVM for JDK 17 (17.0.21.1) and GraalVM EE 21.3.20.1 release notes give a Java 17 base of 17.0.20.1+4, which
   conflicts with the fix; marked REVIEW.
4. The AVX-512 VBMI precondition, the 17.0.6 start, the app lists, the 9.2 score and both flags are news claims; the
   advisories do not state them. The HotSpot source confirms the AVX-512 decode path needs avx512vbmi and avx512bw.
5. `UseBASE64Intrinsics` is a product flag in the HotSpot source and needs no unlock there; Oracle's `java` manual
   says intrinsic flags need `-XX:+UnlockDiagnosticVMOptions`. Use both. `-XX:UseAVX=2` works because `UseAVX < 3`
   clears all AVX-512 features, at a wider performance cost.
6. CNA is Oracle (cve.org), CVSS 3.1 8.1 High; CISA ADP adds CWE-122 and SSVC Exploitation none. NVD status
   Received. Not in KEV.
7. Downstream: Corretto and Azul Zulu have shipped fixes that name the CVE; Temurin and Microsoft had not shipped
   when checked; Red Hat had no CVE page. BleepingComputer's list of affected distributions is a news claim.

## Credits

Research is credited to security researchers only, as reported by BleepingComputer. This pack names no individual
or firm from the OpenJDK or Oracle acknowledgements.

## Sources

- OpenJDK Vulnerability Advisory 2026/11/17: https://openjdk.org/groups/vulnerability/advisories/2026-11-17
- Oracle Critical Security Patch Update, November 2026: https://www.oracle.com/security-alerts/cspunov2026.html
- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114938
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114938
- CISA KEV catalogue: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Oracle JDK release notes: https://www.oracle.com/java/technologies/javase/17-0-21-1-relnotes.html ,
  https://www.oracle.com/java/technologies/javase/21-0-13-1-relnotes.html ,
  https://www.oracle.com/java/technologies/javase/25-0-5-1-relnotes.html ,
  https://www.oracle.com/java/technologies/javase/27-0-1-1-relnotes.html ,
  https://www.oracle.com/java/technologies/javase/8u513-perf-relnotes.html
- Oracle GraalVM release notes: https://docs.oracle.com/en/graalvm/jdk/17/docs/release-notes/ ,
  https://docs.oracle.com/en/graalvm/jdk/21/docs/release-notes/ ,
  https://docs.oracle.com/en/graalvm/enterprise/21/docs/release-notes/
- Oracle `java` manual (JDK 21): https://docs.oracle.com/en/java/javase/21/docs/specs/man/java.html
- Oracle fatal error log: https://docs.oracle.com/en/java/javase/21/troubleshoot/fatal-error-log.html
- Azul Zulu November 2026 release notes: https://docs.azul.com/core/release/november-2026/release-notes
- Adoptium release list: https://api.adoptium.net/v3/info/release_names
- Microsoft Build of OpenJDK release notes: https://learn.microsoft.com/en-us/java/openjdk/release-notes
- Amazon Corretto 17, 21, 25 and 27 change logs (Amazon's Corretto source repositories; not linked here)
- HotSpot source, jdk17u, jdk21u and jdk25u update repositories (files named above; not linked here)
- NEWS: https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/
- MITRE ATT&CK: https://attack.mitre.org/techniques/T1190/ , https://attack.mitre.org/techniques/T1499/004/ ,
  https://attack.mitre.org/techniques/T1071/001/

## Files

`scripts/` checkers; `kql/` hunts; `sigma/` rules and `sigma/converted/`; `tests/` (bash and Pester tests, shared
cases, fixtures marked FIXTURE_ONLY, static and negative gates, `run_all.sh`).
