Code execution or crash via unchecked entry names
Published Aug 5, 2026 · Updated Aug 5, 2026
Stack buffer overflow in rxi microtar allows attackers to corrupt stack memory via archive entry names longer than 99 bytes. The mtar_write_file_header() and mtar_write_dir_header() functions use strcpy() to place a caller-controlled name in a 100-byte stack field without validating its length. Reachability requires an embedding application to pass an externally influenced filename; the overflow can crash that application or enable code execution with its privileges.
Summary
What happened
Stack buffer overflow in rxi microtar allows attackers to corrupt stack memory via archive entry names longer than 99 bytes. The mtar_write_file_header() and mtar_write_dir_header() functions use strcpy() to place a caller-controlled name in a 100-byte stack field without validating its length. Reachability requires an embedding application to pass an externally influenced filename; the overflow can crash that application or enable code execution with its privileges.
The record
- CVE
- CVE-2026-71267
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- rxi
- Product
- microtar
- Classifications
- CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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 <=*
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
No public exploit references are available in this record.
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