CRE-2025-0134

Container exited 134 due to SIGABRT / assertion failureMedium

Impact: 6/10

Mitigation: 2/10

CRE-2025-0134View on GitHub

K8sExit CodeSIGABRTAssertionNative

Description

Exit code 134 indicates the process aborted via SIGABRT, commonly due to failed assertions,\nallocator checks (e.g., glibc detecting heap corruption), or explicit abort() calls.\n

Mitigation

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

References

• https://www.gnu.org/software/libc/manual/html_node/Aborting-a-Program.html