CVE-2026-22801

MEDIUMNVD 6.86.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 93% 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
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.8Exploit: 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 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
1.7%
KEV
Not listed

Published

January 12, 2026

Last Modified

January 21, 2026

References (1)

Vendor Advisories for CVE-2026-22801(20)

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

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibpng16-16t64 (1.6.50-1ubuntu0.3) @ questing2026-05-29ubuntu
ubuntulibpng16-tools (1.6.20-2ubuntu0.1~esm3) @ xenial2026-05-29ubuntu
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhcos-412.86.202604281506-02026-05-08redhat
redhatjava-11-openjdk-1:11.0.31.0.11-1.el92026-04-22redhat
redhatjava-11-openjdk-portable2026-04-22redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-04-17redhat
redhatlibpng-main-1.6.56-1.hum12026-04-07redhat
redhatrhceph/rhceph-8-rhel9:17740028672026-03-24redhat
redhatlibpng-2:1.6.34-8.el8_8.22026-03-17redhat
redhatlibpng-2:1.6.34-8.el8_4.22026-03-17redhat
redhatlibpng-2:1.6.34-8.el8_6.22026-03-17redhat
redhatlibpng-2:1.6.34-8.el8_2.22026-03-17redhat
redhatlibpng-2:1.6.34-10.el8_102026-03-17redhat
redhatdiscovery/discovery-ui-rhel9:17732730702026-03-12redhat
redhatmingw-libpng-0:1.6.34-2.el8_102026-03-11redhat
redhatlibpng-2:1.6.40-8.el10_0.22026-03-03redhat
redhatlibpng-2:1.6.37-12.el9_4.22026-03-03redhat
redhatlibpng-2:1.6.37-12.el9_2.22026-03-03redhat
redhatlibpng-2:1.6.37-12.el9_6.22026-03-03redhat
redhatlibpng-2:1.6.40-8.el10_1.22026-03-02redhat
redhatlibpng-2:1.6.37-12.el9_0.22026-03-02redhat
redhatlibpng-2:1.6.37-12.el9_7.22026-02-26redhat

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

(5)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-22801?
CVE-2026-22801 is a medium vulnerability published on January 12, 2026. LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions pngwriteimage16bit and pngwriteimage8bit causes heap buffer…
When was CVE-2026-22801 disclosed?
CVE-2026-22801 was first published in the National Vulnerability Database on January 12, 2026, with the most recent update on January 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22801 actively exploited?
CVE-2026-22801 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22801?
CVE-2026-22801 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-22801?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22801, 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-2026-22801

Explore →

Is Your Infrastructure Affected by CVE-2026-22801?

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

Start Free Scan →Browse All CVEs