CVE-2026-55738
- Source
- https://cve.org/CVERecord?id=CVE-2026-55738
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-55738.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-55738
- Published
- 2026-06-17T13:45:00.399Z
- Modified
- 2026-07-08T08:09:47.233571271Z
- Severity
-
- 8.7 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CVSS Calculator
- Summary
- Stack Buffer Overflow in rxi/microtar raw_to_header() via non-null-terminated TAR name field
- Details
-
A stack-based buffer overflow exists in the rawtoheader() function in src/microtar.c in rxi microtar 0.1.0. The function copies the 100-byte name and linkname fields of a TAR header with strcpy() without guaranteeing null termination of the source. The POSIX ustar format permits these fixed-width fields to be fully populated with non-null bytes, so a crafted archive whose linkname field (followed by the trailing padding of the 512-byte raw header) contains no null terminator causes strcpy() to read past the end of the 512-byte raw header stack buffer and to write past the destination header buffer. A remote attacker who supplies a crafted TAR archive that the victim opens or parses (via mtaropen(), mtarreadheader(), or mtarfind()) can cause an out-of-bounds read and a stack buffer overflow, resulting in denial of service (crash) and potentially arbitrary code execution. Confirmed with AddressSanitizer: stack-buffer-overflow READ of size 356 in rawtoheader at src/microtar.c:112.
- Database specific
{ "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/55xxx/CVE-2026-55738.json", "cna_assigner": "TuranSec", "cwe_ids": [ "CWE-121", "CWE-170" ] }- References