Elastic Agent and Endpoint Update Prevents Windows Protection Crashes

P2 — VALIDATE AND UPDATEMedium · 6.2 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Elastic published ESA-2026-194 for Elastic Agent and Endpoint on affected Windows locales in 8.19.13-8.19.21, 9.2.7-9.2.8, 9.3.0-9.3.8, 9.4.0-9.4.7, and 9.5.0-9.5.4. Inventory the exact affected scope, apply Elastic Agent and Endpoint 8.19.22, 9.4.8, or 9.5.5, validate dependent operations, and preserve change evidence.

Validate Elastic Agent and Endpoint Scope And Apply The Supported Fix

What to do now: Inventory Elastic Agent and Endpoint on affected Windows locales in 8.19.13-8.19.21, 9.2.7-9.2.8, 9.3.0-9.3.8, 9.4.0-9.4.7, and 9.5.0-9.5.4, match versions and enabled features to the authority's scope, apply supported remediation, validate representative operations, and document exceptions.

Open the authoritative advisory

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

Scope And Authority

Product scopeElastic Agent and Endpoint on affected Windows locales in 8.19.13-8.19.21, 9.2.7-9.2.8, 9.3.0-9.3.8, 9.4.0-9.4.7, and 9.5.0-9.5.4
AdvisoryESA-2026-194
CVECVE-2026-102413
Authoritative release date2026-10-06 18:47:56 UTC
Authority revision date2026-10-06 18:47:56 UTC
Affected versionsThe ESA-listed Windows version ranges under certain locales, including CJK locales, when a crafted filename is processed.
Fixed versionElastic Agent and Endpoint 8.19.22, 9.4.8, or 9.5.5
CVSS base score6.2 (CVSS v3.1)
CVSS severityMedium
Exploitation statusNot stated by the authority; no exploitation claim is inferred.

What Changed

Elastic fixed crafted-filename handling that can crash and restart Endpoint on affected Windows locales, temporarily degrading malware prevention.

What To Validate Now

  1. Inventory. Locate Elastic Agent and Endpoint on affected Windows locales in 8.19.13-8.19.21, 9.2.7-9.2.8, 9.3.0-9.3.8, 9.4.0-9.4.7, and 9.5.0-9.5.4; record versions, enabled features, exposure paths, owners, dependencies, support channels, and maintenance groups.
  2. Establish applicability. Compare every deployment with the authority's affected statement: The ESA-listed Windows version ranges under certain locales, including CJK locales, when a crafted filename is processed. Do not infer applicability from product family, CVSS, or Internet reachability alone.
  3. Remediate. Apply Elastic Agent and Endpoint 8.19.22, 9.4.8, or 9.5.5 through the authority-supported channel and follow the current advisory.
  4. Validate. Confirm the resulting Elastic Agent and Endpoint build or managed state, exercise representative services and recovery paths, monitor for regressions, and retain the result.
  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

Elastic states that no workaround is available. Stage agent upgrades by policy and locale, confirm Endpoint remains healthy, and verify malware-prevention telemetry after deployment. Preserve pre-change state, installation output, logs, validation evidence, and rollback decisions.

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.