# Jdkmap — Java4Shell triage (Thu 19 Nov 2026)

0 of 3 JVMs are exploitable on the evidence supplied. 0 mitigated, 3 not affected. Keep patching normally.

| Name | Product | Java | Affected? | CPU? | Mitigated? | Verdict | Fix |
|---|---|---|---|---|---|---|---|
| arm-api-1 | none | OpenJDK 21.0.13 | Build yes / CPU not exposed | No | No | NOT AFFECTED | — (keep normal patching) |
| old-xeon-1 | jira_dc | OpenJDK 21.0.13 | Yes | No | No | NOT AFFECTED | — (keep normal patching) |
| old-xeon-2 | none | OpenJDK 17.0.21.0.3 | Yes | No | No | NOT AFFECTED | — (keep normal patching) |

## Next steps
1. Thu 19 Nov 2026 (today): no JVM proved exploitable on supplied evidence — keep patching normally.
2. 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.

- arm-api-1 (none): OpenJDK 21.0.13 — NOT AFFECTED. Fix target: — (keep normal patching).
- old-xeon-1 (jira_dc): OpenJDK 21.0.13 — NOT AFFECTED. Fix target: — (keep normal patching).
- old-xeon-2 (none): OpenJDK 17.0.21.0.3 — 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.
