CVE-2019-20053

MEDIUMNVD 5.55.5—

5.5

An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.

CVSS v3: 5.5
EG Score: 5.5(medium)
EPSS: 57.7%
KEV: Not listed

Published

December 27, 2019

Last Modified

April 11, 2025

References (6)

cve@mitrehttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00003.html
cve@mitrehttp://lists.opensuse.org/opensuse-security-announce/2020-02/msg00007.html
cve@mitrehttps://github.com/upx/upx/issues/314
af854a3a-2127-422b-91ae-364da2661108http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00003.html
af854a3a-2127-422b-91ae-364da2661108http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00007.html
af854a3a-2127-422b-91ae-364da2661108https://github.com/upx/upx/issues/314

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 20× 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.

2026-06-08 14:15 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-05 22:45 UTCEPSS rescore
2026-06-05 22:45 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-02 20:11 UTCEPSS rescore
2026-06-02 20:11 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-29 13:42 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-20053?

CVE-2019-20053 is a medium vulnerability published on December 27, 2019. An invalid memory address dereference was discovered in the canUnpack function in p_mach.cpp in UPX 3.95 via a crafted Mach-O file.

When was CVE-2019-20053 disclosed?

CVE-2019-20053 was first published in the National Vulnerability Database on December 27, 2019, with the most recent update on April 11, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-20053 actively exploited?

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

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

CVE-2019-20053 has a CVSS v3 base score of 5.5 (NVD).

How do I remediate CVE-2019-20053?

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

Explore →

Is Your Infrastructure Affected by CVE-2019-20053?

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

Start Free Scan →Browse All CVEs

CVE-2019-20053

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-20053?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)