GHSA-j7hp-h8jx-5ppr is a high-severity (CVSS 8.8) Out-of-bounds Write vulnerability in libwebp-sys2. 26 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-j7hp-h8jx-5ppr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
libwebp: OOB write in BuildHuffmanTable
Exploitation Status
Actively exploited in the wild
- CISA’s SSVC triage classifies this CVE as under active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j7hp-h8jx-5ppr.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-j7hp-h8jx-5ppr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 369,023 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
libwebp-sys2🦀libwebp-sys🦀webp🐹github.com/chai2010/webp🐹github.com/chai2010/webp🐹github.com/chai2010/webp📦electron📦electron+11 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Heap buffer overflow in libwebp allow a remote attacker to perform an out of bounds memory write via a crafted HTML page.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | libwebp-sys2 | all versions | 0.1.8 |
| 🦀crates.io | libwebp-sys | all versions | 0.9.3 |
| 🦀crates.io | webp | all versions | 0.2.6 |
| 🐹Go | github.com/chai2010/webp | ≥ 1.1.2&&< 1.4.0 | 1.4.0 |
| 🐹Go | github.com/chai2010/webp | all versions | 0.0.0-20250406010349-76805d5a8860 |
| 🐹Go | github.com/chai2010/webp | ≥ 0.0.0&&< 1.1.2-0.20250406010349-76805d5a8860 | 1.1.2-0.20250406010349-76805d5a8860 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libwebp-sys2. 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 libwebp-sys2 to 0.1.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7hp-h8jx-5ppr 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-j7hp-h8jx-5ppr 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-j7hp-h8jx-5ppr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This security issue has been classified as having an Important security impact. Desktop users are at a high risk of exploitation of this flaw with very minimal interaction. It may compromise the confidentiality, integrity, or availability of resources. Customers using this application, which does server-side image…
Frequently Asked Questions
Is GHSA-j7hp-h8jx-5ppr in your dependencies?
O3 detects GHSA-j7hp-h8jx-5ppr across crates.io, Go, npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.