Vulnerability in Bep Imagemeta
CVE-2026-103025
- CVSS
- Not scored
- Public exploits
- 1 repository
- EPSS
- Not scored yet
- Published
- 2026-11-19
What to do
- Fixed in
0.17.3- Affected
- 1 affected product
bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. Prior to 0.17.3, imagemeta.Decode could exhaust memory when parsing PNG zTXt chunks whose keyword is "Raw profile type iptc": the declared chunk length can drive an allocation far larger than the input file, and the embedded zlib stream is decompressed without an output limit. The advisory reports a 42-byte input causing a 256 MB allocation and a 127 KB input inflating to 460 MB. The oversized-allocation path's memory effect depends on platform overcommit and configured GOMEMLIMIT or cgroup limits, while the decompression path reliably creates resident memory. Applications that decode untrusted PNGs with IPTC metadata processing can therefore suffer denial of service through memory exhaustion. This issue is fixed in 0.17.3.
Published · last modified .
EPSS exploit prediction
FIRST.org has not scored this CVE yet. About EPSS.
Affected products
- Bep Imagemeta — versions < 0.17.3
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- googlesky/CVE-2026-103025 (last pushed 2026-11-20): bep/imagemeta <0.17.3: PNG zTXt iptc path allocates from declared chunk length and inflates zlib unbounded — a 65KB PNG allocates ~471MB (memory-exhaustion DoS). Real Decode from v0.17.2 vs vendor-fi…