CVE-2026-111273: unarr through 1.1.1 Off-by-One Heap Buffer Overflow via tar_get_name

Published Oct 15, 2026
·
Updated

unarr through 1.1.1 contains an off-by-one heap-based buffer overflow in targetname() in tar/parse-tar.c, reachable through the arentrygetname() API. Attackers can supply a crafted TAR archive with a full ustar prefix and name to write a NUL byte past the allocation, corrupting heap memory and crashing the process.

Affected Software

1 affected component
unarr unarr<=1.1.1

Event History

Oct 15, 2026
CVE Published
via MITRE·09:43 PM
Data Sourced
via MITRE·09:43 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What does an attacker need to exploit this issue?

An attacker needs to provide a crafted TAR archive whose ustar prefix and name fields are full. Exploitation is reachable when the application processes the archive through the ar_entry_get_name() API, and user interaction is required according to the supplied severity vector.

2

Which versions are affected?

unarr through version 1.1.1 is affected.

3

What is the likely impact?

The crafted archive causes tar_get_name() to write a NUL byte one byte past a heap allocation. This can corrupt heap memory and crash the process; the supplied severity vector indicates low integrity impact and high availability impact.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203