Summary
bep/imagemeta allows a potentially large memory allocation in PNG and WebP parsing
Impact
The buffer created for parsing metadata for PNG and WebP images was only bounded by their input data type, which could lead to potentially large memory allocation, and unreasonably high for image metadata. Before v0.11.0, If you didn't trust the input images, this could be abused to construct denial-of-service attacks.
The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
v0.11.0 added a 10 MB upper limit.
Frequently Asked Questions
- What is CVE-2025-32025? CVE-2025-32025 is a medium-severity allocation of resources without limits or throttling vulnerability in github.com/bep/imagemeta (go), affecting versions < 0.11.0. It is fixed in 0.11.0. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
- Which versions of github.com/bep/imagemeta are affected by CVE-2025-32025? github.com/bep/imagemeta (go) versions < 0.11.0 is affected.
- Is there a fix for CVE-2025-32025? Yes. CVE-2025-32025 is fixed in 0.11.0. Upgrade to this version or later.
- Is CVE-2025-32025 exploitable, and should I be worried? Whether CVE-2025-32025 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-32025 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-32025? Upgrade
github.com/bep/imagemetato 0.11.0 or later.