Read the docs

Recursive memory allocation in Exiv2 PGF metadata reading

Priority LOW 38CWE-121Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

Exiv2 versions up to and including 0.28.8 contain a flaw in PgfImage::readMetadata() that causes recursive memory allocation. An attacker can trigger it by providing a malicious PGF file that a user opens with Exiv2, such as by running exiv2 on it. The allocation consumes a very large amount of memory and can degrade system performance.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

A denial-of-service was found in `PgfImage::readMetadata()`. See https://github.com/Exiv2/exiv2/issues/9419 for more details about the cause of the bug. The vulnerability can be triggered by running Exiv2 on a malicious file, like this: ```bash exiv2 poc.pgf ``` This causes Exiv2 to rapidly allocate a very large amount of memory, which can impact system performance.

Why it matters now

Fix Fixed exiv2: 0.28.9

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—exiv2<= 0.28.80.28.9Patch availableGHSA-pwvq-9w4q-786w
  • exiv2 Vendor— Affected <= 0.28.8 Fixed in 0.28.9 Patch available GHSA-pwvq-9w4q-786w

Remediation

Update exiv2 to version 0.28.9, which fixes this flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-pwvq-9w4q-786w exiv2 Fixed in 0.28.9 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-pwvq-9w4q-786w

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences