How severe is GHSA-fmhh-rw3h-785m?

No CVSS score has been assigned to GHSA-fmhh-rw3h-785m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fmhh-rw3h-785m?

GHSA-fmhh-rw3h-785m affects the following packages: github.com/bep/imagemeta (Go). Ecosystems affected: Go.

How do I fix GHSA-fmhh-rw3h-785m?

Update github.com/bep/imagemeta to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmhh-rw3h-785m is resolved across your whole dependency graph.

How do I detect GHSA-fmhh-rw3h-785m in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bep/imagemeta. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fmhh-rw3h-785m if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fmhh-rw3h-785m?

O3 pinpoints whether GHSA-fmhh-rw3h-785m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fmhh-rw3h-785m actively exploited in the wild?

No public exploit code has been indexed for GHSA-fmhh-rw3h-785m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-fmhh-rw3h-785m?

GHSA-fmhh-rw3h-785m has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 5th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-fmhh-rw3h-785m?

GHSA-fmhh-rw3h-785m is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fmhh-rw3h-785m published, and has it been updated?

GHSA-fmhh-rw3h-785m was published on April 9, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-fmhh-rw3h-785m

bep/imagemeta allows a potentially large memory allocation in PNG and WebP parsing

Also known asCVE-2025-32025GO-2025-3599

Published

Apr 9, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk5th percentile-0.10%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/bep/imagemeta

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

v0.11.0 added a 10 MB upper limit.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/bep/imagemeta`	all versions	0.11.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/bep/imagemeta. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/bep/imagemeta to 0.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fmhh-rw3h-785m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fmhh-rw3h-785m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fmhh-rw3h-785m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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. ### Patches `v0.11.0` added a 10 MB upper limit.

O3 Security · Impact-Aware SCA

Is GHSA-fmhh-rw3h-785m in your dependencies?

O3 detects GHSA-fmhh-rw3h-785m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works