Skip to main content

CRE-2025-0134

Container exited 134 due to SIGABRT / assertion failureMedium
Impact: 6/10
Mitigation: 2/10

CRE-2025-0134View on GitHub

Description

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.


Cause

  • assert(false) / std::abort() in C/C++.
  • Memory allocator consistency errors (double free, corruption).
  • Defensive abort on unrecoverable invariant violations.

Mitigation

  • Enable core dumps and symbols; capture backtraces.
  • Run ASAN/UBSAN builds in staging to localize corruption.
  • Pin and verify libc/libstdc++ versions; roll back recent native changes.

References