CVE-2025-65018

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
12.9%
KEV
Not listed

Published

November 25, 2025

Last Modified

June 17, 2026

References (7)

Vendor Advisories for CVE-2025-65018(17)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpng16-tools (1.6.20-2ubuntu0.1~esm2) @ xenial2026-05-29ubuntu
redhatlibpng-main-1.6.56-1.hum12026-04-07redhat
redhatjava-25-openjdk-1:25.0.2.0.10-1.el92026-01-26redhat
redhatjava-17-openjdk-portable2026-01-26redhat
redhatjava-25-openjdk-portable2026-01-26redhat
redhatjava-21-openjdk-portable2026-01-26redhat
redhatjava-1.8.0-openjdk-1:1.8.0.482.b08-1.el92026-01-26redhat
redhatjava-1.8.0-openjdk-portable2026-01-26redhat
redhatjava-21-openjdk-1:21.0.10.0.7-1.el92026-01-22redhat
redhatjava-17-openjdk-1:17.0.18.0.8-1.el92026-01-22redhat
redhatpatch2026-01-21redhat
redhatjava-11-openjdk-1:11.0.30.0.7-1.el92026-01-21redhat
redhatjava-11-openjdk-portable2026-01-21redhat
redhatlibpng-2:1.6.34-8.el8_4.12026-01-08redhat
redhatlibpng-2:1.6.34-8.el8_6.12026-01-08redhat
redhatlibpng-2:1.6.34-8.el8_2.12026-01-08redhat
redhatdiscovery/discovery-ui-rhel9:17679045732026-01-08redhat
redhatlibpng-2:1.6.34-8.el8_8.12026-01-08redhat
redhatlibpng-2:1.6.37-12.el9_7.12026-01-07redhat
redhatlibpng-2:1.6.37-12.el9_4.12026-01-07redhat
redhatlibpng-2:1.6.34-9.el8_102026-01-07redhat
redhatlibpng-2:1.6.37-12.el9_0.12026-01-07redhat
redhatlibpng-2:1.6.37-12.el9_2.12026-01-07redhat
redhatlibpng-2:1.6.40-8.el10_1.12026-01-07redhat
redhatlibpng-2:1.6.40-8.el10_0.12026-01-07redhat
redhatlibpng-2:1.6.37-12.el9_6.12026-01-07redhat
redhatmingw-libpng-0:1.6.34-1.el8_102026-01-06redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 50× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 09:11 UTCOSV refresh
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-04 06:30 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 42 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-17 21:14 UTCOSV refresh
  10. 2026-06-17 17:52 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-15 17:48 UTCEPSS rescore
  13. 2026-06-15 17:48 UTCEPSS rescore
  14. 2026-06-14 23:18 UTCEPSS rescore
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-13 23:00 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-08 14:17 UTCEPSS rescore
  23. 2026-06-08 14:16 UTCEPSS rescore
  24. 2026-06-07 15:24 UTCEPSS rescore
  25. 2026-06-07 15:24 UTCEPSS rescore
  26. 2026-06-06 13:47 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-05 22:46 UTCEPSS rescore
  29. 2026-06-05 22:46 UTCEPSS rescore
  30. 2026-06-05 06:10 UTCEPSS rescore
  31. 2026-06-05 06:10 UTCEPSS rescore
  32. 2026-06-04 13:12 UTCEPSS rescore
  33. 2026-06-04 13:12 UTCEPSS rescore
  34. 2026-06-02 20:13 UTCEPSS rescore
  35. 2026-06-02 20:12 UTCEPSS rescore
  36. 2026-06-01 13:51 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-05-31 22:30 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-29 18:53 UTCEG score recompute
  41. 2026-05-29 18:53 UTCVendor advisory
  42. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCNeo-Neo6/CVE-2025-65018-Heap-buffer-overflow-in-libpng-ps4-ps5-
    First seen Nov 23, 2025
    Open source ↗

Frequently asked(5)

What is CVE-2025-65018?
CVE-2025-65018 is a high vulnerability published on November 25, 2025. LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function pngimagefinish_read when processing…
When was CVE-2025-65018 disclosed?
CVE-2025-65018 was first published in the National Vulnerability Database on November 25, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-65018 actively exploited?
CVE-2025-65018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-65018?
CVE-2025-65018 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-65018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-65018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-65018

Explore →

Is Your Infrastructure Affected by CVE-2025-65018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs