Tag: SIGABRT

Crashes where a process aborts with SIGABRT (exit 134), often due to assertion failures or allocator checks.

ID	Title	Description	Category	Technology	Tags
CRE-2025-0134 Medium Impact: 6/10 Mitigation: 2/10	Container exited 134 due to SIGABRT / assertion failure	Exit code 134 indicates the process aborted via SIGABRT, commonly due to failed assertions, allocator checks (e.g., glibc detecting heap corruption), or explicit abort() calls.	Runtime	kubernetes	K8s Exit Code SIGABRT Assertion Native