Finding and attribution
The PromeFuzz authors report that the system discovered this use-after-free in Exiv2 through a generated harness for Exiv2::TiffParser::encode. Their paper traces it to a shallow copy of TiffSubIfd::ifds_ and later traversal of freed entries in doAccept. Exiv2’s advisory describes a heap buffer overflow when writing metadata to a crafted image; its CLI requires an additional operation such as fixiso. The advisory says code execution may be possible if a victim is tricked into running Exiv2 on the crafted image.
Product: Exiv2. AI system: PromeFuzz (LLM-based fuzzing harness generation; per-case model not identified). Team / organization: Institute of Software, Chinese Academy of Sciences / Ant Group research team; Exiv2 maintainers.
CVE identifiers: CVE-2025-26623.
AI and human contribution (source account): The PromeFuzz paper explicitly attributes discovery of CVE-2025-26623 to PROMEFUZZ and explains that LLM-supported API understanding enabled generation of the TiffParser::encode harness. It does not identify the model used for this case or the human review steps for this particular finding.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The Exiv2 security advisory was published 2025-02-18. The cited sources do not report exploitation in the wild or establish whether defenders knew the issue before discovery.
Remediation status: fix documented. The Exiv2 advisory identifies issue #3168 and references preliminary PR #3174; maintainer PR #3179 follows that revert and replaces raw pointers with std::unique_ptr to fix the ownership defect. The advisory states version 0.28.5 is patched; the release was published 2025-02-21. This does not establish deployed patch status.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 18 Feb 2025. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: code execution.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
CVE-2025-26623: code execution.
Prerequisites / affected scope: Exiv2 versions 0.28.0 through 0.28.4; metadata writing on a crafted image. For the command-line utility, the advisory says an additional argument such as fixiso is needed. The source says code execution may be possible if an attacker tricks a victim into running Exiv2 on the crafted file..
Exploitation evidence: Potential code execution is described by the Exiv2 advisory; exploitation in the wild is not reported in the cited sources.. Impact source · checked 17 Nov 2026.
Documented fix: The Exiv2 advisory identifies issue #3168 and references preliminary PR #3174; maintainer PR #3179 follows that revert and replaces raw pointers with std::unique_ptr to fix the ownership defect. The advisory states version 0.28.5 is patched; the release was published 2025-02-21. This does not establish deployed patch status.