cve.bz

CVE-2026-103025 bep/imagemeta: Unbounded memory allocation decoding PNG `zTXt` "Raw profile type iptc" chunks

8.7 highEPSS 0.6%Fix available

High (8.7) in bep imagemeta. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/bep/imagemeta 0.17.3.

On this page
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.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/bep/imagemeta (Go): fixed in 0.17.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-103025 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-103025?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-103025?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-103025 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bep imagemeta< 0.17.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7hvw-3c2q-45qgGogithub.com/bep/imagemeta<0.17.30.17.3

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • googlesky/CVE-2026-103025 Harbor Check: matches CVE 0 stars, Python, created
    bep/imagemeta <0.17.3: PNG zTXt iptc path allocates from declared chunk length and inflates zlib unbounded — a 65KB PNG allocates ~471MB (m…

References

Check your stackJSON