Skip to main content
Menu
CVEs

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.

CVE-2026-103025Published November 19, 2026, updated

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.17.3
Who is exposed
Not reported

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

Original 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.

Who should check

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

“A crafted PNG can make imagemeta.Decode allocate memory far in excess of the input file's size”

github.com

What to do

  1. Upgrade to a fixed version: 0.17.3.

  2. Workaround: Reject or bound PNG input size before calling Decode, or clear IPTC from Options.Sources if IPTC metadata is not required.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Affected versions

cve.now Index

29Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · bep/imagemeta · Advisory GHSA-7hvw-3c2q-45qg
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-103025
RecordNVD · CVE-2026-103025
Other links 3
RepositoryGitHub · bep/imagemeta · Pull request #69
RepositoryGitHub · bep/imagemeta · Commit 2289fdf8
RepositoryGitHub · bep/imagemeta · Release v0.17.3

Questions about CVE-2026-103025

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-103025?

imagemeta: before 0.17.3.

Source: cve.now feed data

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: github.com

How do I fix CVE-2026-103025?

Upgrade to a fixed version: 0.17.3.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.