Tag: Exit Code

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

ID	Title	Description	Category	Technology	Tags
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 Problem	kubernetes	K8s Exit Code Command Entrypoint Startup 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.	Runtime	kubernetes	K8s Exit Code SIGABRT Assertion Native
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 Problems	kubernetes	K8s Exit Code Out of Memory Memory Crash Loop Reliability
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.	Runtime	kubernetes	K8s Exit Code Segfault Native Reliability