CVE-2025-26623: Use After Free in Exiv2

Published Feb 18, 2025
·
Updated

Impact A heap buffer overflow was found in Exiv2 versions v0.28.0 to v0.28.4. Versions prior to v0.28.0, such as v0.27.7, are not affected. Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. The heap overflow is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentially exploit the vulnerability to gain code execution, if they can trick the victim into running Exiv2 on a crafted image file.

Note that this bug is only triggered when writing the metadata, which is a less frequently used Exiv2 operation than reading the metadata. For example, to trigger the bug in the Exiv2 command-line application, you need to add an extra command-line argument such as fixiso.

Patches The bug is fixed in version v0.28.5.

References Issue: https://github.com/Exiv2/exiv2/issues/3168 Fix: https://github.com/Exiv2/exiv2/pull/3174

For more information Please see our security policy for information about Exiv2 security.

Other sources

Exiv2 is a C++ library and a command-line utility to read, write, delete and modify Exif, IPTC, XMP and ICC image metadata. A heap buffer overflow was found in Exiv2 versions v0.28.0 to v0.28.4. Versions prior to v0.28.0, such as v0.27.7, are not affected. Exiv2 is a command-line utility and C++ library for reading, writing, deleting, and modifying the metadata of image files. The heap overflow is triggered when Exiv2 is used to write metadata into a crafted image file. An attacker could potentially exploit the vulnerability to gain code execution, if they can trick the victim into running Exiv2 on a crafted image file. Note that this bug is only triggered when writing the metadata, which is a less frequently used Exiv2 operation than reading the metadata. For example, to trigger the bug in the Exiv2 command-line application, you need to add an extra command-line argument such as fixiso. The bug is fixed in version v0.28.5. Users are advised to upgrade. There are no known workarounds for this vulnerability.

MITRE

Affected Software

3 affected componentsFixes available
pip/Exiv2>=0.28.0<0.28.5
0.28.5
exiv2 exiv2>=0.28.0<0.28.5
exiv2 exiv2>=0.28.0<0.28.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/Exiv2 to a version that resolves this vulnerability.

    Fixed in 0.28.5
  2. Upgrade

    Upgrade Exiv2 to a version that resolves this vulnerability.

    Fixed in v0.28.5

Event History

Feb 18, 2025
CVE Published
via MITRE·07:24 PM
Data Sourced
via MITRE·07:24 PM
DescriptionWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
Affected Software
Feb 21, 2025
Advisory Published
via GitHub·11:53 PM
May 19, 58462
Event
via NVD·07:11 AM
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-2025-26623?

CVE-2025-26623 has been rated with a high severity due to the potential for a heap buffer overflow.

2

How do I fix CVE-2025-26623?

To fix CVE-2025-26623, upgrade Exiv2 to version 0.28.5 or later.

3

Which versions of Exiv2 are affected by CVE-2025-26623?

Exiv2 versions from 0.28.0 to 0.28.4 are affected by CVE-2025-26623.

4

Is Exiv2 version 0.27.7 affected by CVE-2025-26623?

No, Exiv2 version 0.27.7 is not affected by CVE-2025-26623.

5

What types of vulnerabilities does CVE-2025-26623 involve?

CVE-2025-26623 involves a heap buffer overflow vulnerability.

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