# Jdkmap — Java4Shell triage (Thu 19 Nov 2026)

3 of 8 JVMs are exploitable now — fix keycloak-1 (internet-facing identity provider) first, to Keycloak 26.8.2-3 (bundles JDK 21.0.13.1): Eclipse Temurin 21.0.13 with Base64 intrinsics on an exposed CPU. 1 mitigated, 3 not affected, 1 unknown.

| Name | Product | Java | Affected? | CPU? | Mitigated? | Verdict | Fix |
|---|---|---|---|---|---|---|---|
| keycloak-1 | keycloak | Eclipse Temurin 21.0.13 | Yes | Yes | No | EXPLOITABLE | Keycloak 26.8.2-3 (bundles JDK 21.0.13.1) |
| es-node-1 | elasticsearch | OpenJDK 27.0.1 | Yes | Yes | No | EXPLOITABLE | Elasticsearch 9.4.10 (bundles JDK 27.0.1.1+4) |
| es-node-2 | elasticsearch | OpenJDK 27.0.1 | Yes | Yes | No | EXPLOITABLE | Elasticsearch 9.4.10 (bundles JDK 27.0.1.1+4) |
| legacy-app-1 | other | OpenJDK 21.0.13 | Yes | Unknown | No | UNKNOWN | 21.0.13.1 |
| jira-dc-1 | jira_dc | Oracle 17.0.21.0.3 | Yes | Yes | Yes | MITIGATED | Atlassian release bundling a fixed JRE (check Atlassian); interim flag now |
| build-agent | none | Amazon Corretto 11.0.29 | No | Yes | No | NOT AFFECTED | — (keep normal patching) |
| confluence-dc-1 | confluence_dc | Oracle 17.0.21.1 | No | Yes | No | NOT AFFECTED | — (keep normal patching) |
| graviton-api | none | OpenJDK 21.0.13 | Build yes / CPU not exposed | No | No | NOT AFFECTED | — (keep normal patching) |

## Next steps
1. Thu 19 Nov 2026 (today): apply interim flag and restart exploitable JVMs, internet-facing/IdP first: keycloak-1, es-node-1, es-node-2.
2. Thu 19 Nov 2026 (today, same day): verify each restarted JVM live the same day as the interim flag (jcmd VM.flags / product check) and record java -version output: keycloak-1, es-node-1, es-node-2.
3. Fri 20 Nov 2026: collect missing info for unknowns (legacy-app-1) — java -version, CPU flags line, live jcmd flags.
4. Sat 21 Nov 2026 (within 2 days): patch window — upgrade exploitable internet-facing/IdP JVMs to the fix targets listed per JVM: keycloak-1 (planning defaults (not from an advisory)).
5. Thu 26 Nov 2026 (within 7 days): patch window — upgrade other exploitable JVMs to the fix targets listed per JVM: es-node-1, es-node-2 (planning defaults (not from an advisory)).
6. Thu 3 Dec 2026 (next patch window, asOf + 14 days): patch mitigated JVMs: jira-dc-1 (planning defaults (not from an advisory)). Keep interim flags on mitigated JVMs until patched; remove flag after patch only when vendor says.
7. Watch CISA KEV — status: not in KEV at disclosure (third-party). Do not assume current status; check CISA.

## Change ticket

Change ticket — Java4Shell CVE-2026-114938 triage, Thu 19 Nov 2026

I checked each JVM below for Java build, CPU flags and effective JVM flags.

- keycloak-1 (keycloak 26.8.2-1): Eclipse Temurin 21.0.13 — EXPLOITABLE. Fix target: Keycloak 26.8.2-3 (bundles JDK 21.0.13.1). Interim: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (preferred; restart required); alternative x86-64 only: -XX:UseAVX=2. Where: JAVA_OPTS_APPEND (append, do not replace); Operator JVM needs JDK_JAVA_OPTIONS separately. Verify: jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics  (expect: bool UseBASE64Intrinsics = false).
- es-node-1 (elasticsearch 9.4.9): OpenJDK 27.0.1 — EXPLOITABLE. Fix target: Elasticsearch 9.4.10 (bundles JDK 27.0.1.1+4). Interim: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (preferred; restart required); alternative x86-64 only: -XX:UseAVX=2. Where: config/jvm.options.d/cve-2026-114938.options with one line -XX:-UseBASE64Intrinsics (Elastic); ECK: ES_JAVA_OPTS. Verify: Check -XX:-UseBASE64Intrinsics appears in jvm.input_arguments in GET _nodes/jvm output (Elastic).
- es-node-2 (elasticsearch 9.4.9): OpenJDK 27.0.1 — EXPLOITABLE. Fix target: Elasticsearch 9.4.10 (bundles JDK 27.0.1.1+4). Interim: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (preferred; restart required); alternative x86-64 only: -XX:UseAVX=2. Where: config/jvm.options.d/cve-2026-114938.options with one line -XX:-UseBASE64Intrinsics (Elastic); ECK: ES_JAVA_OPTS. Verify: Check -XX:-UseBASE64Intrinsics appears in jvm.input_arguments in GET _nodes/jvm output (Elastic).
- legacy-app-1 (other): OpenJDK 21.0.13 — UNKNOWN. Fix target: 21.0.13.1. Interim: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (preferred; restart required); alternative x86-64 only: -XX:UseAVX=2. Where: Your service JVM options (JAVA_OPTS / JDK_JAVA_OPTIONS / service unit), preserving existing options. Verify: jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics  (expect false) — note: java -XX:+PrintFlagsFinal -version starts a new JVM and does not prove the running service.
- jira-dc-1 (jira_dc): Oracle 17.0.21.0.3 — MITIGATED. Fix target: Atlassian release bundling a fixed JRE (check Atlassian); interim flag now. Interim: -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics (preferred; restart required); alternative x86-64 only: -XX:UseAVX=2. Where: Atlassian DC: follow Atlassian mitigation page for your product (setenv/JVM_SUPPORT_RECOMMENDED_ARGS per product); Atlassian lists -XX:UseAVX=2 with -XX:+IgnoreUnrecognizedVMOptions (x86-64 only). Bundled JRE — host package updates alone do not fix it. Verify: jcmd <pid> VM.flags -all | grep -F UseBASE64Intrinsics  (expect false) — note: java -XX:+PrintFlagsFinal -version starts a new JVM and does not prove the running service.
- build-agent (none): Amazon Corretto 11.0.29 — NOT AFFECTED. Fix target: — (keep normal patching).
- confluence-dc-1 (confluence_dc): Oracle 17.0.21.1 — NOT AFFECTED. Fix target: — (keep normal patching).
- graviton-api (none): OpenJDK 21.0.13 — NOT AFFECTED. Fix target: — (keep normal patching).

Rollback: if a service fails after adding the flag, I will remove the added flag, restart, and confirm the service health checks pass; I will not remove pre-existing JVM options.
Verification evidence I will attach: post-restart java -version output, CPU flags line, and live jcmd VM.flags output (or Elasticsearch GET _nodes/jvm) for each JVM.
Note: host names above are as I entered them in Jdkmap and are stored in a shared report only if I choose to share it.

Jdkmap · Daily Ships · Triage aid, not a security guarantee. Version, CPU and flag rules follow the OpenJDK, Oracle, Red Hat and CERT advisories (checked 19 Nov 2026); your vendor's advisory decides.
