CVE-2019-6129

MEDIUMNVD 6.56.5—Trending — 3 sources updated this week

6.5

png_create_info_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.

CVSS v3: 6.5
EG Score: 6.5(medium)
EPSS: 52.0%
KEV: Not listed

Published

January 11, 2019

Last Modified

May 28, 2026

References (4)

cve@mitrehttps://github.com/glennrp/libpng/issues/269
cve@mitrehttps://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
af854a3a-2127-422b-91ae-364da2661108https://github.com/glennrp/libpng/issues/269
af854a3a-2127-422b-91ae-364da2661108https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html

Weakness Classification(1)

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

CWE-401Missing Release of Memory after Effective Lifetime (Memory Leak)

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 23:28 UTCEG score recompute
2026-05-27 23:28 UTCGHSA enrichment
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 10:43 UTCOSV refresh
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-6129?

CVE-2019-6129 is a medium vulnerability published on January 11, 2019. pngcreateinfo_struct in png.c in libpng 1.6.36 has a memory leak, as demonstrated by pngcp. NOTE: a third party has stated "I don't think it is libpng's job to free this buffer.

When was CVE-2019-6129 disclosed?

CVE-2019-6129 was first published in the National Vulnerability Database on January 11, 2019, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-6129 actively exploited?

CVE-2019-6129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-6129?

CVE-2019-6129 has a CVSS v3 base score of 6.5 (NVD).

How do I remediate CVE-2019-6129?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-6129, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-6129

Explore →

Is Your Infrastructure Affected by CVE-2019-6129?

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

Start Free Scan →Browse All CVEs

CVE-2019-6129

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-6129?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)