Skip to main content

Tag: Native

Issues in native code paths (C/C++/Rust, libc/ABI), including crashes and memory faults.

IDTitleDescriptionCategoryTechnologyTags
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-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