CVE-2018-0501

Name: CVE-2018-0501
Creator: NVD / NIST
Published: 2018-08-21T00:29:00.227+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 0.95%

Last modified Jun 17, 2026

CVE-2018-0501 is a vulnerability of currently unknown severity. The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.. EPSS estimates a 0.95% chance of exploitation in the next 30 days.

Description

The mirror:// method implementation in Advanced Package Tool (APT) 1.6.x before 1.6.4 and 1.7.x before 1.7.0~alpha3 mishandles gpg signature verification for the InRelease file of a fallback mirror, aka mirrorfail.

Metrics

EPSS Probability

0.95%

56.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-347

Affected Software

Vendor	Product	Versions	Update
Canonical	Ubuntu Linux	18.04	—
Debian	Advanced Package Tool	>= 1.6.0, < 1.6.4	—
Debian	Advanced Package Tool	1.7.0	Alpha

References

https://mirror.failThird Party Advisory, URL Repurposed
https://salsa.debian.org/apt-team/apt/commit/29658a3a74af49e2a24e17bdebb20e1612aac3ecPatch, Third Party Advisory
https://salsa.debian.org/apt-team/apt/commit/aebd4278bacc728ab00ebe31556983e140f60e47Patch, Third Party Advisory
https://usn.ubuntu.com/3746-1/Third Party Advisory
https://mirror.failThird Party Advisory, URL Repurposed
https://salsa.debian.org/apt-team/apt/commit/29658a3a74af49e2a24e17bdebb20e1612aac3ecPatch, Third Party Advisory
https://salsa.debian.org/apt-team/apt/commit/aebd4278bacc728ab00ebe31556983e140f60e47Patch, Third Party Advisory
https://usn.ubuntu.com/3746-1/Third Party Advisory

Timeline

Published: Aug 21, 2018
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2018-0501?

How severe is CVE-2018-0501?

Severity scoring for CVE-2018-0501 is pending analysis. The EPSS model estimates a 0.95% probability of exploitation in the next 30 days.

How do I fix CVE-2018-0501?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2018-0501?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST