CVE-2026-15028: Libarchive: heap overflow oob read while parsing a tar archive contains a pax extended header

Published Jul 8, 2026
·
Updated

A flaw was found in libarchive. This vulnerability allows a remote attacker to trigger a heap overflow by providing a specially crafted tar archive. The issue occurs during the parsing of a PAX extended header containing a malformed SUN.holesdata sparse-file attribute. Successful exploitation could lead to a denial of service, making the system unavailable, or potentially allow for arbitrary code execution, giving the attacker control over the affected system.

Other sources

Hello Red Hat PSIRT,

I would like to request CVE assignment for a security vulnerability I found in libarchive.

There is a heap overflow problem while parsing a tar archive that contains a PAX extended header with the SUN.holesdata sparse-file attribute. headerpaxextension() passes the attribute value to paxattribute() with the trailing newline excluded from the value length. The SUN.holesdata parser later treats the byte after the supplied value as if it were still part of the accessible buffer and reads it when length == 0.

More detail can be found in github issue: https://github.com/libarchive/libarchive/issues/3251 A fixed PR has been commit: https://github.com/libarchive/libarchive/pull/3253

Until send this email, I have search no public report of this flaw. I want to know if it can be assgned a CVE ID or do you need any other more detail informations.

Best regards, Bon Voyage

Red Hat

Libarchive: heap overflow oob read while parsing a tar archive contains a pax extended header

Microsoft

Affected Software

2 affected componentsFixes available
Libarchive libarchive
Microsoft azl3 libarchive 3.7.7-6<3.7.7-7
3.7.7-7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.7.7-7

Event History

Jul 8, 2026
Data Sourced
via Red Hat·07:06 AM
DescriptionSeverityAffected Software
Jul 10, 2026
CVE Published
via MITRE·09:55 AM
Data Sourced
via MITRE·09:55 AM
DescriptionSeverity
Data Sourced
via NVD·10:16 AM
DescriptionSeverityWeakness
Jul 15, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-15028?

The severity of CVE-2026-15028 is rated as low with a score of 3.9.

2

How do I fix CVE-2026-15028?

To mitigate CVE-2026-15028, it is recommended to update to the latest version of libarchive that addresses this vulnerability.

3

What kind of attack is possible with CVE-2026-15028?

CVE-2026-15028 allows a remote attacker to trigger a heap overflow by sending a specially crafted tar archive.

4

Which software is affected by CVE-2026-15028?

CVE-2026-15028 affects the Libarchive library used for handling archive files.

5

What is the impact of exploiting CVE-2026-15028?

Successful exploitation of CVE-2026-15028 could lead to a potential denial of service or arbitrary code execution.

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