CVE-2019-0160

CRITICALNVD 9.89.8—

9.8

Buffer overflow in system firmware for EDK II may allow unauthenticated user to potentially enable escalation of privilege and/or denial of service via network access.

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 51.5%
KEV: Not listed

Published

March 27, 2019

Last Modified

November 21, 2024

References (2)

secure@intelhttps://tianocore-docs.github.io/SecurityAdvisory/draft/partitiondxe-and-udf-buffer-overflow.html
af854a3a-2127-422b-91ae-364da2661108https://tianocore-docs.github.io/SecurityAdvisory/draft/partitiondxe-and-udf-buffer-overflow.html

Patch Availability(3)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
ubuntu	qemu-efi (0~20160408.ffea0a2c-2ubuntu0.2+esm1) @ xenial	2026-05-27	ubuntu
redhat	edk2-0:20190308git89910a39dcfd-6.el8	2019-11-05	redhat
redhat	ovmf-0:20180508-6.gitee3198e672e2.el7	2019-08-06	redhat

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.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-05-27 21:20 UTCEG score recompute
2026-05-27 21:20 UTCVendor advisory
2026-05-27 21:20 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 11:13 UTCOSV refresh
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-0160?

CVE-2019-0160 is a critical vulnerability published on March 27, 2019. Buffer overflow in system firmware for EDK II may allow unauthenticated user to potentially enable escalation of privilege and/or denial of service via network access.

When was CVE-2019-0160 disclosed?

CVE-2019-0160 was first published in the National Vulnerability Database on March 27, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-0160 actively exploited?

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

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

CVE-2019-0160 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2019-0160?

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

Explore →

Is Your Infrastructure Affected by CVE-2019-0160?

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

Start Free Scan →Browse All CVEs

CVE-2019-0160

Published

Last Modified

References (2)

Patch Availability(3)

Weakness Classification(2)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-0160?

Same vendor

Same CWE

CVE-2019-0160

📅 Published

🔄 Last Modified

🔗 References (2)

Patch Availability(3)

Weakness Classification(2)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-0160?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same vendor + same CWE)