CVE-2018-14550 — libpng
HIGHCVE-2018-14550 is a high-severity (CVSS 8.8) Out-of-bounds Write vulnerability in libpng. 2 public exploit references exist, so weaponization risk is real. A fix is available for libpng — see the affected versions and patch details below.
Out-of-bounds write in libpng
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2018-14550 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
libpngReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
An issue has been found in third-party PNM decoding associated with libpng 1.6.35. It is a stack-based buffer overflow in the function get_token in pnm2png.c in pnm2png.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | libpng | all versions | 1.6.37dotnet add package libpng --version 1.6.37 |
Affected Products
libpnglibpngactive iq unified managernetapponcommand api servicesnetapphyperion infrastructure technologyoraclemysql workbenchoracleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libpng, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libpng to 1.6.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14550 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.
Frequently Asked Questions
Is CVE-2018-14550 in your dependencies?
Find it across NuGet, including transitive dependencies.