Stack corruption via oversized safe_strcpy length
Published Aug 28, 2026 · Updated Aug 28, 2026
Stack buffer overflow in Ericsson CodeChecker 6.26.2 through 6.28.2 allows local users to corrupt stack memory during build logging. In ldlogger-tool-gcc.c, loggerMakePathAbs passes fullPath + 2 to safe_strcpy with PATH_MAX, so strncpy NUL-pads 4,096 bytes into the 4,094 bytes remaining. The local path is reachable through CC_LOGGER_DEF_DIRS and fires on every CodeChecker log invocation, but only two fixed zero bytes are written and no control-flow hijack is demonstrated.
Summary
What happened
Stack buffer overflow in Ericsson CodeChecker 6.26.2 through 6.28.2 allows local users to corrupt stack memory during build logging. In ldlogger-tool-gcc.c, loggerMakePathAbs passes fullPath + 2 to safe_strcpy with PATH_MAX, so strncpy NUL-pads 4,096 bytes into the 4,094 bytes remaining. The local path is reachable through CC_LOGGER_DEF_DIRS and fires on every CodeChecker log invocation, but only two fixed zero bytes are written and no control-flow hijack is demonstrated.
The record
- CVE
- CVE-2026-58106
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- Vendor
- Ericsson
- Product
- CodeChecker
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2026CVE publishedPublication date reported by the CVE source.
- Aug 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=6.28.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- AddressSanitizer stack-overflow reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo