CVE-2019-15989

HIGHNVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under NVD CVSS v3. EPSS exploit probability: 2.5%, top 14% 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
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability in the implementation of the Border Gateway Protocol (BGP) functionality in Cisco IOS XR Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to incorrect processing of a BGP update message that contains a specific BGP attribute. An attacker could exploit this vulnerability by sending BGP update messages that include a specific, malformed attribute to be processed by an affected system. A successful exploit could allow the attacker to cause the BGP process to restart unexpectedly, resulting in a DoS condition. The Cisco implementation of BGP accepts incoming BGP traffic only from explicitly defined peers. To exploit this vulnerability, the malicious BGP update message would need to come from a configured, valid BGP peer or would need to be injected by the attacker into the victim’s BGP network on an existing, valid TCP connection to a BGP peer.

CVSS v3
8.6
EG Score
8.6(medium)
EPSS
67.3%
KEV
Not listed

Published

January 26, 2020

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 42× 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-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-08 15:11 UTCEPSS rescore
  4. 2026-07-07 13:42 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-04 06:28 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-02 16:56 UTCEPSS rescore
  11. 2026-07-01 15:03 UTCEPSS rescore
  12. 2026-07-01 15:03 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-29 14:03 UTCEPSS rescore
  16. 2026-06-28 14:04 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-28 04:53 UTCEPSS rescore
  19. 2026-06-27 03:06 UTCEPSS rescore
  20. 2026-06-27 03:06 UTCEPSS rescore
  21. 2026-06-25 13:47 UTCEPSS rescore
  22. 2026-06-25 13:47 UTCEPSS rescore
  23. 2026-06-24 14:03 UTCEPSS rescore
  24. 2026-06-24 14:02 UTCEPSS rescore
  25. 2026-06-23 21:30 UTCEPSS rescore
Show 48 more
  1. 2026-06-23 21:30 UTCEPSS rescore
  2. 2026-06-22 14:23 UTCEPSS rescore
  3. 2026-06-22 14:23 UTCEPSS rescore
  4. 2026-06-21 14:54 UTCEPSS rescore
  5. 2026-06-21 14:54 UTCEPSS rescore
  6. 2026-06-21 01:57 UTCEPSS rescore
  7. 2026-06-21 01:57 UTCEPSS rescore
  8. 2026-06-19 19:23 UTCEPSS rescore
  9. 2026-06-19 19:23 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:45 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-12 23:09 UTCEPSS rescore
  18. 2026-06-11 13:58 UTCEPSS rescore
  19. 2026-06-11 13:58 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-10 13:19 UTCEPSS rescore
  22. 2026-06-08 14:15 UTCEPSS rescore
  23. 2026-06-08 14:14 UTCEPSS rescore
  24. 2026-06-07 15:23 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
  26. 2026-06-06 13:45 UTCEPSS rescore
  27. 2026-06-06 13:45 UTCEPSS rescore
  28. 2026-06-05 22:45 UTCEPSS rescore
  29. 2026-06-05 22:45 UTCEPSS rescore
  30. 2026-06-05 06:08 UTCEPSS rescore
  31. 2026-06-05 06:08 UTCEPSS rescore
  32. 2026-06-04 13:10 UTCEPSS rescore
  33. 2026-06-04 13:10 UTCEPSS rescore
  34. 2026-06-02 20:11 UTCEPSS rescore
  35. 2026-05-31 22:29 UTCEPSS rescore
  36. 2026-05-31 22:29 UTCEPSS rescore
  37. 2026-05-31 00:14 UTCEPSS rescore
  38. 2026-05-31 00:14 UTCEPSS rescore
  39. 2026-05-29 13:42 UTCEPSS rescore
  40. 2026-05-28 13:43 UTCEPSS rescore
  41. 2026-05-27 13:38 UTCEPSS rescore
  42. 2026-05-27 08:41 UTCEG score recompute
  43. 2026-05-27 08:41 UTCGHSA enrichment
  44. 2026-05-26 13:42 UTCEPSS rescore
  45. 2026-05-26 13:42 UTCEPSS rescore
  46. 2026-05-26 07:17 UTCEPSS rescore
  47. 2026-05-26 07:17 UTCEPSS rescore
  48. 2026-05-25 03:37 UTCOSV refresh

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-15989?
CVE-2019-15989 is a high vulnerability published on January 26, 2020. A vulnerability in the implementation of the Border Gateway Protocol (BGP) functionality in Cisco IOS XR Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. The vulnerability is due to incorrect processing of a BGP update message that contains a…
When was CVE-2019-15989 disclosed?
CVE-2019-15989 was first published in the National Vulnerability Database on January 26, 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-15989 actively exploited?
CVE-2019-15989 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 67.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-15989?
CVE-2019-15989 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2019-15989?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-15989, 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-15989

Explore →

Is Your Infrastructure Affected by CVE-2019-15989?

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

Start Free Scan →Browse All CVEs