Elastic Publishes Java4Shell Mitigations for Elasticsearch and Logstash

P2 — VALIDATE AND UPDATENot provided by the authority · Not provided by the authorityEXPLOITATION: NOT STATED

Quick Answer

Match Java, CPU and data-processing conditions, apply Elastic’s supported Base64-intrinsic mitigation, and verify each restarted node or process.

Confirm Scope And Apply The Supported Remediation

What to do now: Record Elastic versions, deployment model, JVM configuration, CPU capabilities, Kubernetes node placement and Logstash filter pipelines. Distinguish self-managed nodes from Elastic-managed services. Elastic says Serverless was hotfixed and only a small Azure subset of Cloud Hosted is affected; do not generalize this to all hosted deployments. For affected self-managed processes, apply -XX:-UseBASE64Intrinsics through the product-specific configuration described by Elastic, then perform the required controlled restart. Follow separate ECK, ECE and hosted guidance. Verify Elasticsearch jvm.input_arguments through GET _nodes/jvm and Logstash bootstrap flags. Retain configuration, restart and cluster-health evidence.

Open the authoritative advisory

Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeElasticsearch and Logstash deployments using affected Java and CPU configurations
AdvisoryElastic-Java4Shell-2026-11-18
CVECVE-2026-114938
Authoritative release date2026-11-18T22:01:58Z — Elastic security-announcement feed.
Authority revision dateNo separate material revision is stated for this release.
Affected versionsElasticsearch 7.17.3 and later and Logstash 8.6.2 and later on affected x86-64 CPUs with AVX-512 VBMI. Logstash exposure additionally requires the elastic_integration filter processing attacker-controlled Base64 through an Elasticsearch ingest pipeline.
Fixed versionVendor-supported interim mitigation: disable Base64 intrinsics and restart affected processes; announced fixed Elastic releases are pending
CVSS base scoreNot provided by the authority
CVSS severityNot provided by the authority
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Elastic confirmed product-specific exposure and supplied mitigations. Elasticsearch code execution requires an authenticated user with read access; denial of service can be unauthenticated. The stated Logstash path permits denial of service. Announced releases 8.19.26, 9.4.10, 9.5.7 and 9.6.0 are upcoming, not confirmed available fixes.

What To Validate Now

  1. Inventory. Record Elastic versions, deployment model, JVM configuration, CPU capabilities, Kubernetes node placement and Logstash filter pipelines.
  2. Establish applicability. Distinguish self-managed nodes from Elastic-managed services. Elastic says Serverless was hotfixed and only a small Azure subset of Cloud Hosted is affected; do not generalize this to all hosted deployments.
  3. Remediate. For affected self-managed processes, apply -XX:-UseBASE64Intrinsics through the product-specific configuration described by Elastic, then perform the required controlled restart. Follow separate ECK, ECE and hosted guidance.
  4. Validate. Verify Elasticsearch jvm.input_arguments through GET _nodes/jvm and Logstash bootstrap flags. Retain configuration, restart and cluster-health evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Preserve existing JVM settings and use the documented negative flag. Kubernetes rescheduling can change CPU exposure. Do not describe upcoming builds as already released; recheck vendor availability before upgrading.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.