# CVE-2025-32024: bep/imagemeta allows excessively large EXIF data structures

> Attackers can cause denial of service by providing malicious images with excessively large EXIF structures to applications using the vulnerable Go library.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-q7rw-w4cq-2j6w, GO-2025-3598

## What is CVE-2025-32024?

CVE-2025-32024 is a medium-severity denial of service vulnerability in bep imagemeta, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. The EXIF data format allows for defining excessively large data structures in relatively small payloads. Before v0.10.0, If you didn't trust the input images, this could be abused to construct denial-of-service attacks. v0.10.0 added LimitNumTags (default 5000) and LimitTagSize (default 10000) options.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2025-32024?

3 open source packages ship an affected version, including github.com/bep/imagemeta.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/bep/imagemeta` | Go | All versions | 0.10.0 |
| `github.com/bep/imagemeta` | Go | All versions | 0.10.0 |
| `github.com/bep/imagemeta` | Go | All versions | 0.10.0 |

## How do I fix CVE-2025-32024?

Upgrade github.com/bep/imagemeta to 0.10.0 or later.

## Is CVE-2025-32024 being exploited?

There is no known exploitation of CVE-2025-32024 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32024 and fix it if it is affected.

What it is: CVE-2025-32024 is a medium-severity denial of service vulnerability in bep imagemeta, published on 8 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-32024 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/bep/imagemeta (Go): affected all versions; fixed in 0.10.0
- github.com/bep/imagemeta (Go): affected all versions; fixed in 0.10.0
- github.com/bep/imagemeta (Go): affected all versions; fixed in 0.10.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-32024/ (Markdown: https://insights.sbomify.com/CVE-2025-32024/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32024
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32024
- OSV: https://osv.dev/vulnerability/CVE-2025-32024

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-32024/
Summaries are generated and may contain mistakes; the official description above is the record.