CVE-2019-13917

CVE-2019-13917 is a critical-severity vulnerability in Exim with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-19.

Key facts

Description

Exim 4.85 through 4.92 (fixed in 4.92.1) allows remote code execution as root in some unusual configurations that use the ${sort } expansion for items that can be controlled by an attacker (e.g., $local_part or $domain).

Frequently asked questions

What is CVE-2019-13917?
Exim 4.85 through 4.92 (fixed in 4.92.1) allows remote code execution as root in some unusual configurations that use the ${sort } expansion for items that can be controlled by an attacker (e.g., $local_part or $domain).
How severe is CVE-2019-13917?
CVE-2019-13917 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-13917 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 9% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-13917?
CVE-2019-13917 primarily affects Exim. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-13917?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-13917 published?
CVE-2019-13917 was published on 2019-07-25 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Exim

All CVEs affecting Exim →

Other CWE-19 vulnerabilities

Browse all CWE-19 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: