Skip to main content

Tag: Exit Code

Problems identified by specific process/container exit codes (e.g., 137, 127, 134, 139).

IDTitleDescriptionCategoryTechnologyTags
CRE-2025-0127
Medium
Impact: 3/10
Mitigation: 3/10
Container exited 127 due to command not found (bad entrypoint/command)
Exit code 127 indicates the configured command/entrypoint was not found in the image or PATH.New or misconfigured deployments commonly hit this and immediately crash.
Configuration Problemk8sK8sExit CodeCommandEntrypointStartup Failure
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.
Runtimek8sK8sExit CodeSIGABRTAssertionNative
CRE-2025-0137
High
Impact: 6/10
Mitigation: 2/10
Pod terminated with Exit Code 137 due to OOMKilled (memory limit exceeded)
The container exceeded its memory limit and was killed by the kernel OOM killer.Kubernetes reports a terminated state with Reason=OOMKilled and exitCode=137.This often manifests as CrashLoopBackOff under sustained memory pressure.
Memory Problemsk8sK8sExit CodeOut of MemoryMemoryCrash LoopReliability
CRE-2025-0139
Medium
Impact: 7/10
Mitigation: 2/10
Container exited 139 due to segmentation fault (SIGSEGV)
Exit code 139 indicates SIGSEGV (invalid memory access) in native/runtime code.Frequently caused by unsafe pointer operations, ABI/library mismatches, or native extensions.
Runtimek8sK8sExit CodeSegfaultNativeReliability