CVE-2019-18634

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 19.4%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 19%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

In Sudo before 1.8.26, if pwfeedback is enabled in /etc/sudoers, users can trigger a stack-based buffer overflow in the privileged sudo process. (pwfeedback is a default setting in Linux Mint and elementary OS; however, it is NOT the default for upstream and many other packages, and would exist only if enabled by an administrator.) The attacker needs to deliver a long string to the stdin of getln() in tgetpass.c.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
97.1%
KEV
Not listed

Published

January 29, 2020

Last Modified

November 21, 2024

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntusudo (1.8.9p5-1ubuntu1.5+esm3) @ trusty2026-05-27ubuntu
ubuntusudo-ldap (1.8.16-0ubuntu1.9) @ xenial2026-05-27ubuntu
redhatsudo-0:1.8.6p3-29.el6_10.32020-03-05redhat
redhatsudo-0:1.8.23-4.el7_7.22020-02-19redhat
redhatsudo-0:1.8.25p1-8.el8_1.12020-02-14redhat
redhatsudo-0:1.8.25p1-4.el8_0.32020-02-14redhat

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(1)

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

All Vendor Advisories

(6)

Data Freshness Timeline

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

  1. 2026-07-25 14:14 UTCEPSS rescore
  2. 2026-07-24 14:14 UTCEPSS rescore
  3. 2026-07-24 14:14 UTCEPSS rescore
  4. 2026-07-23 14:15 UTCEPSS rescore
  5. 2026-07-23 01:42 UTCEG score recompute
  6. 2026-07-22 22:22 UTCEG score recompute 1.20
  7. 2026-07-22 14:05 UTCEPSS rescore
  8. 2026-07-21 15:22 UTCEPSS rescore
  9. 2026-07-21 15:22 UTCEPSS rescore
  10. 2026-07-20 17:04 UTCEPSS rescore
  11. 2026-07-20 17:04 UTCEPSS rescore
  12. 2026-07-19 20:48 UTCOSV refresh
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-19 02:26 UTCEPSS rescore
  15. 2026-07-18 10:01 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-16 16:59 UTCEPSS rescore
  18. 2026-07-15 16:55 UTCEPSS rescore
  19. 2026-07-15 16:55 UTCEPSS rescore
  20. 2026-07-13 22:27 UTCEPSS rescore
  21. 2026-07-13 06:10 UTCEPSS rescore
  22. 2026-07-13 06:10 UTCEPSS rescore
  23. 2026-07-12 05:43 UTCEPSS rescore
  24. 2026-07-12 05:43 UTCEPSS rescore
  25. 2026-07-11 08:24 UTCEPSS rescore
Show 59 more
  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-07 13:43 UTCEPSS rescore
  4. 2026-07-06 16:25 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-05 02:27 UTCEPSS rescore
  8. 2026-07-02 11:12 UTCOSV refresh
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-07-01 15:03 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-28 04:54 UTCEPSS rescore
  14. 2026-06-27 03:06 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-21 14:54 UTCEPSS rescore
  23. 2026-06-21 14:54 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-21 01:57 UTCEPSS rescore
  26. 2026-06-19 19:23 UTCEPSS rescore
  27. 2026-06-19 19:23 UTCEPSS rescore
  28. 2026-06-18 17:50 UTCEPSS rescore
  29. 2026-06-17 17:50 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 17:45 UTCEPSS rescore
  32. 2026-06-14 23:15 UTCEPSS rescore
  33. 2026-06-14 23:15 UTCEPSS rescore
  34. 2026-06-14 09:43 UTCOSV refresh
  35. 2026-06-12 23:09 UTCEPSS rescore
  36. 2026-06-10 22:16 UTCEPSS rescore
  37. 2026-06-10 13:19 UTCEPSS rescore
  38. 2026-06-08 14:15 UTCEPSS rescore
  39. 2026-06-07 15:23 UTCEPSS rescore
  40. 2026-06-07 15:23 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 22:45 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-04 13:10 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-05-29 13:42 UTCEPSS rescore
  50. 2026-05-28 13:43 UTCEPSS rescore
  51. 2026-05-27 08:27 UTCEG score recompute
  52. 2026-05-27 08:27 UTCVendor advisory
  53. 2026-05-27 08:27 UTCGHSA enrichment
  54. 2026-05-26 18:31 UTCOSV refresh
  55. 2026-05-26 13:42 UTCEPSS rescore
  56. 2026-05-26 13:42 UTCEPSS rescore
  57. 2026-05-26 07:17 UTCEPSS rescore
  58. 2026-05-26 07:17 UTCEPSS rescore
  59. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(7 references)

Working exploit code is in the public domain (5 GitHub PoCs) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCchanbakjsd/CVE-2019-18634
    First seen Apr 14, 2024

    A reproduction of CVE-2019-18634, sudo privilege escalation with buffer overflow.

    Open source ↗
  • GitHub PoCaesophor/CVE-2019-18634
    First seen Aug 1, 2021

    My n-day exploit for CVE-2019-18634 (local privilege escalation)

    Open source ↗
  • GitHub PoCN1et/CVE-2019-18634
    First seen Feb 13, 2020

    An Python Exploit for Sudo vulnerability CVE-2019-18634

    Open source ↗
  • GitHub PoCPlazmaz/CVE-2019-18634
    First seen Feb 7, 2020

    A functional exploit for CVE-2019-18634, a BSS overflow in sudo's pwfeedback feature that allows for for privesc

    Open source ↗
  • GitHub PoCsaleemrashid/sudo-cve-2019-18634
    First seen Feb 7, 2020

    Proof of Concept for CVE-2019-18634

    Open source ↗
  • Exploit-DBEDB-48052
    First seen Feb 6, 2020

    Sudo 1.8.25p - 'pwfeedback' Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-47995
    First seen Feb 4, 2020

    Sudo 1.8.25p - 'pwfeedback' Buffer Overflow (PoC)

    Open source ↗

Frequently asked(5)

What is CVE-2019-18634?
CVE-2019-18634 is a high vulnerability published on January 29, 2020. In Sudo before 1.8.26, if pwfeedback is enabled in /etc/sudoers, users can trigger a stack-based buffer overflow in the privileged sudo process. (pwfeedback is a default setting in Linux Mint and elementary OS; however, it is NOT the default for upstream and many other packages, and would exist…
When was CVE-2019-18634 disclosed?
CVE-2019-18634 was first published in the National Vulnerability Database on January 29, 2020, 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-18634 actively exploited?
CVE-2019-18634 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-18634?
CVE-2019-18634 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2019-18634?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-18634, 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

Explore the affected products and dependency analysis for CVE-2019-18634

Explore →

Is Your Infrastructure Affected by CVE-2019-18634?

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