CVEHit Business Advisory by IntegrityLab.ai
What should we do?
Java4Shell: Java flaw can let attackers take over some servers — CVE-2026-114938: Business Triage
Do Now
- System owner: install the November 17 Java update (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1 or your vendor's matching release) and restart Java applications, starting with Internet-facing services and Java programs that connect out to outside servers.
Proof the update is done
- Start with Internet-facing services, including the products Calif names (Keycloak, Jira, Confluence, Artifactory, Jenkins, PingFederate).
- The Java version reported by the running application after restart, not just the installed package. Source and date.
- For bundled Java, the product vendor's notice naming CVE-2026-114938.
- Operations owner: where an immediate update is not possible, apply a temporary control and record it.
What to know
- CISA: restrict and validate Base64 input at the application boundary, enforce input-size limits, and limit unauthenticated access.
- The reporting researchers say starting Java with -XX:-UseBASE64Intrinsics turns off the affected decoder, or -XX:UseAVX=2 turns off AVX-512. Use -XX:UseAVX=2 only on x86-64; Java on ARM will not start with it.
- These are stopgaps, not the fix, and are not listed by Oracle.
- Provider: ask each vendor whose product, appliance or hosted service includes Java whether it is affected and when a fix ships.
What to ask
- Ask for:
- Java vendor and version inside the product.
- Processor type where it runs.
- The fix date.
- Keep the reply as evidence.
Do Next
- Security owner: recheck CISA and Oracle for changes to the exploitation status.
What to recheck
- CISA's assessment in the CVE record, dated November 17, 2026.
- The CISA KEV catalog. CVE-2026-114938 was not in catalog 2026.11.18.
- The reporting researchers say they are holding back product-specific exploit details for now and will publish them later. Recheck when that happens.
- Date of each recheck.
← Back to article questions