CVE-2026-111273 selmf CVE debrief

Who should care

Defenders responsible for systems or applications using the unarr library should assess exposure and prioritize patching or mitigation efforts. This includes verifying the version of unarr in use, reviewing system logs for potential exploitation attempts, and implementing additional security measures, such as input validation and error handling. Defenders should also review the supplied official advisory or CVE record to validate affected scope, severity,

Why it matters

This vulnerability can lead to a process crash and potential heap memory corruption, allowing attackers to potentially exploit the system. Defenders should prioritize verifying the version of unarr in use and applying patches or updates to mitigate this vulnerability.

• Verify and apply patches or updates to prevent potential exploitation.
• Monitor system logs for potential exploitation attempts.
• Implement additional security measures, such as input validation and error handling.

Technical summary

The tar_get_name() function in unarr through 1.1.1 is vulnerable to an off-by-one heap-based buffer overflow. This can be exploited by supplying a crafted TAR archive with a full ustar prefix and name, leading to a process crash and potential heap memory corruption. The vulnerability is caused by an off-by-one error in the tar_get_name() function, which can be triggered by a specially crafted TAR archive. Defenders should prioritize verifying the version of unarr in use and applying patches or updates to mitigate this vulnerability.

Defensive priority

Defenders should prioritize verifying the version of unarr in use and applying patches or updates to mitigate this vulnerability.

Recommended defensive actions

• Verify the version of unarr in use and apply patches or updates to mitigate this vulnerability.
• Review and monitor system logs for potential exploitation attempts.
• Implement additional security measures, such as input validation and error handling, to prevent similar vulnerabilities.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description and affected versions. However, there is limited information on potential exploits or impacts. The vulnerability is caused by an off-by-one error in the tar_get_name() function, which can be triggered by a specially crafted TAR archive. Defenders should verify the version of unarr in use and apply patches or updates to mitigate this vulnerability. The CVE record and source item provide details on the vulnerability, including its description,

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.