Quick answers
- Is CVE-2025-26623 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-26623 being exploited in the wild.
- How severe is CVE-2025-26623?
- Medium severity, with a CVSS score of 4, published 7 July 2026.
- Which products and versions are affected?
- exiv2 (PyPI) ECOSYSTEM:introduced=0.28.0,fixed=0.28.5.
- Is there a fix for CVE-2025-26623?
- Yes. exiv2 (PyPI): upgrade to 0.28.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-26623 attacked?
- It is attacked over the network.
- Am I affected by CVE-2025-26623?
- Check whether you run exiv2 (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- exiv2 (PyPI): upgrade to 0.28.5 or later
pip install "exiv2>=0.28.5"
Technical details
A use-after-free vulnerability (CWE-416) exists in the TiffSubIfd component of Exiv2 versions 0.28.0 through 0.28.4. The flaw is triggered specifically during metadata write operations (not read) on a specially crafted image file. An attacker must social-engineer a victim into executing an Exiv2 command with a write operation flag (e.g., `fixiso`) on the malicious image. The vulnerability can result in heap buffer overflow and potential remote code execution. The bug is fixed in version 0.28.5, and versions prior to 0.28.0 are not affected.
Affected products
- Exiv2 Exiv2 0.28.0 to 0.28.4
Identifiers
- CVE-2025-26623
- GHSA-38h4-fx85-qcx7
- PYSEC-2026-1353
Timeline
- 2025-02-18: disclosed: NVD published date
- 2025-02-21: disclosed: GitHub advisory GHSA-38h4-fx85-qcx7 published
- 2025-02-21: patched: Fix released in version 0.28.5