Java HotSpot Fatal Error Log Created

Last updated a day ago on 2026-11-18
Created a day ago on 2026-11-18

About

Identifies the creation of a Java HotSpot fatal error log by a Java process. The JVM writes "hs_err_pid*.log" after a fatal error, such as an access violation, segmentation fault, or unrecoverable native-code failure. This may indicate an unsuccessful attempt to exploit a Java memory-corruption vulnerability. In particular, failed Java4Shell (CVE-2026-114938) heap-grooming or corruption attempts may crash the JVM before remote code execution succeeds. This event indicates a JVM crash and possible exploit attempt; it does not by itself establish successful exploitation or remote code execution.
Tags
Domain: EndpointOS: WindowsOS: LinuxOS: macOSUse Case: Threat DetectionUse Case: VulnerabilityTactic: Initial AccessTactic: ExecutionTactic: ImpactData Source: Elastic DefendData Source: Auditd ManagerData Source: Microsoft Defender XDRData Source: SentinelOneData Source: CrowdstrikeRule Type: Event Correlation (EQL)Platform: WindowsPlatform: LinuxPlatform: macOSVuln: CVE-2026-114938Language: eql
Severity
medium
Risk Score
47
MITRE ATT&CK™

Initial Access (TA0001)(external, opens in a new tab or window)

Execution (TA0002)(external, opens in a new tab or window)

Impact (TA0040)(external, opens in a new tab or window)

False Positive Examples
JVM defects, incompatible or vulnerable JNI libraries, Java agents, profilers, faulty native modules, hardware problems, and resource exhaustion can legitimately cause HotSpot to terminate and write a fatal error log.
License
Elastic License v2(external, opens in a new tab or window)

Definition

Rule Type
Event Correlation Rule
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
logs-endpoint.events.file-*auditbeat-*logs-auditd_manager.auditd-*logs-m365_defender.event-*logs-sentinel_one_cloud_funnel.*logs-crowdstrike.fdr*
Related Integrations

endpoint(external, opens in a new tab or window)

auditd_manager(external, opens in a new tab or window)

m365_defender(external, opens in a new tab or window)

sentinel_one_cloud_funnel(external, opens in a new tab or window)

crowdstrike(external, opens in a new tab or window)

Query
text code block:
file where host.os.type in ("windows", "linux", "macos") and event.type == "creation" and process.name : "java*" and file.name : "hs_err_pid*.log"

Install detection rules in Elastic Security

Detect Java HotSpot Fatal Error Log Created in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(external, opens in a new tab or window).