Skip to main content
VulnerabilityPublished

CVE-2026-103025: bep imagemeta · Excessive Memory Allocation

Affects bep imagemetaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 0.17.3 soon.

Data as of 19 Nov 2026, 20:06 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 0.17.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade bep imagemeta to 0.17.3.

Affected software

ProductAffectedFixed in
bepimagemetaAffected
  • <0.17.3
Fixed in
  • 0.17.3

AI-suggested

Upgrade bep/imagemeta to version 0.17.3 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause of excessive memory allocation and decompression limits.

Description

A memory exhaustion vulnerability exists in the bep/imagemeta Go library prior to version 0.17.3. The issue occurs when parsing PNG zTXt chunks with the keyword "Raw profile type iptc", where the declared chunk length can cause excessive memory allocation and decompression without output limits. This can lead to denial of service via memory exhaustion. The vulnerability is fixed in version 0.17.3.

References

Community reviews

Loading reviews…