CVE-2026-73639

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 49% 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: cisa-adp, epss
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Imager::File::PNG versions from 1.003 before 1.004 for Perl write past the end of the row buffer reading a PNG with a tRNS transparency chunk in read_direct8.

With a tRNS chunk, read_direct8() adds an alpha channel to the image it creates but still sizes the row buffer from the original channel count. libpng expands the transparency into that extra channel, so png_read_row() fills one channel more than the buffer holds, at one byte per sample, and writes width bytes past the end of the allocation. Palette images go to read_paletted() and 16-bit images to read_direct16(), which sizes its buffer from png_get_rowbytes() and allocates enough for the expanded row.

The same reader ships bundled in the Imager distribution.

Reading an attacker-supplied PNG through Imager->read() corrupts the heap, which can crash the process.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 22, 2026

Advisory Details (5)

Auto-updated Sep 22, 2026
Patch available. Sources: github, github_pr.
github_pr

PNG vchannels conversion incomplete

Upstream fix in progress (PR #567 · tonycoz/imager, state=closed)

https://github.com/tonycoz/imager/pull/567
github Patch Available

Buffer write overflow decoding 8-bit per sample PNG files with a tRNS chunk · Advisory · tonycoz/imager · GitHub

https://github.com/tonycoz/imager/security/advisories/GHSA-jhx5-34j8-9g88

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 14× 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-09-24 16:23 UTCEG score recompute
  2. 2026-09-23 18:04 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 18:33 UTCEG score recompute▲ 9.10
  5. 2026-09-22 18:33 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  6. 2026-09-21 21:09 UTCEPSS rescore
  7. 2026-09-21 14:19 UTCEG score recompute
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 01:29 UTCNVD update
  11. 2026-09-18 00:29 UTCMITRE cvelistV5
  12. 2026-09-17 22:22 UTCNVD update
  13. 2026-09-17 21:24 UTCEG score recompute
  14. 2026-09-17 21:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-73639?
CVE-2026-73639 is a critical vulnerability published on September 17, 2026. Imager::File::PNG versions from 1.003 before 1.004 for Perl write past the end of the row buffer reading a PNG with a tRNS transparency chunk in read_direct8. With a tRNS chunk, readdirect8() adds an alpha channel to the image it creates but still sizes the row buffer from the original channel…
When was CVE-2026-73639 disclosed?
CVE-2026-73639 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73639 actively exploited?
CVE-2026-73639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.8% of all scored CVEs.
What is the CVSS score of CVE-2026-73639?
CVE-2026-73639 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-73639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73639, 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-73639

Explore →

Is Your Infrastructure Affected by CVE-2026-73639?

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