Summary
Exiv2 allows Use After Free
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.
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.
Memory is accessed after it has been freed, leading to undefined behavior in native code. Typical impact: memory corruption, crash, or potential code execution.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The bug is fixed in version v0.28.5.
Frequently Asked Questions
- What is CVE-2025-26623? CVE-2025-26623 is a medium-severity use after free vulnerability in Exiv2 (pip), affecting versions >= 0.28.0, < 0.28.5. It is fixed in 0.28.5. Memory is accessed after it has been freed, leading to undefined behavior in native code.
- Which versions of Exiv2 are affected by CVE-2025-26623? Exiv2 (pip) versions >= 0.28.0, < 0.28.5 is affected.
- Is there a fix for CVE-2025-26623? Yes. CVE-2025-26623 is fixed in 0.28.5. Upgrade to this version or later.
- Is CVE-2025-26623 exploitable, and should I be worried? Whether CVE-2025-26623 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-26623 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-26623? Upgrade
Exiv2to 0.28.5 or later.