CVE-2026-58106

LowCVSS 2.0

Published: 28/08/2026(UTC)Updated: 28/08/2026(UTC)Translated: 28/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.13%

3th percentile - higher than 3% of all known CVEs

Summary

In CodeChecker through 6.28.2, there is a flaw in ldlogger-tool-gcc.c:129 where the safe_strcpy() helper (which is strncpy()) writes 4096 bytes into a buffer of 4094 bytes, causing a 2-byte stack overflow on every invocation, independent of the input path's length. The fix for CVE-2025-40843 replaced unchecked strcpy() with a bounded safe_strcpy(), but the size passed was incorrect.

Risk Assessment

The risk includes potential stack overflow, which could lead to program crash or arbitrary code execution by an attacker.

Recommendation

It is recommended to update CodeChecker to a version containing the complete fix and avoid using vulnerable versions.

Other vulnerabilities in CodeChecker

CVE-2026-58107Medium
CodeChecker's massStoreRun processing path performs one-shot decompression of attacker-controlled, Base64-encoded zlib data without enforcing a maximum decompressed size. An authenticated user with permission to store analysis runs can submit a highly compressed payload that expands to a significantly larger byte sequence. Because the entire decompressed output is materialized in memory before being written to a temporary file, a sufficiently large payload may exhaust process or host memory and consume substantial disk space, resulting in denial of service.

Original NVD description (English source)

CVE-2025-40843 https://github.com/advisories/GHSA-5xf2-f6ch-6p8r was fixed by replacing unchecked strcpy() with a bounded safe_strcpy() helper. At ldlogger-tool-gcc.c:129 the destination passed to that helper is fullPath + 2, but the size passed down is the full PATH_MAX. safe_strcpy() is strncpy(), which NUL-pads the destination out to the whole n, so this site writes 4096 bytes into the 4094 that remain — a 2-byte stack overflow on every invocation, independent of the input path's length. This issue affects CodeChecker: through 6.28.2.