CVE-2026-71267
Stack buffer overflow in microtar allows code execution via long filenames
Is CVE-2026-71267 being exploited?
Not confirmed. CVE-2026-71267 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-71267?
CVE-2026-71267 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71267?
Not known from our data. No patch reference has been recorded for CVE-2026-71267, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71267 affect?
CVE-2026-71267 affects microtar (src/microtar.c), Applications using microtar to create archives, Embedded devices bundling microtar. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71267?
Update microtar when patched; meanwhile validate/truncate filenames to <=99 chars and block untrusted inputs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Stack-based buffer overflow in mtar_write_* lets attacker-supplied long filenames cause crash or arbitrary code execution in apps using microtar.
Immediate action required
- affected<= *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.