CVE-2019-25724

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-02. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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

Dräger Infinity M300 patient worn monitors with software version VG2.x and earlier contain a network-based denial of service vulnerability that allows attackers with access to the hospital or Infinity Network to repeatedly trigger device reboots until the device enters a fail state requiring manual restart. Attackers can exploit this vulnerability to cause loss of wireless network connectivity, temporary loss of patient monitoring, and interruption of alarm functionality until the device is manually recovered.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

Dräger Infinity M300 VG2.x Network-Based Denial of Service | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dr-ger-infinity-m300-vg2-x-network-based-denial-of-service

Vendor Advisories for CVE-2019-25724(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 114 total refreshes for this CVE.

  1. 2026-07-28 03:36 UTCEG score recompute
  2. 2026-07-28 03:35 UTCGHSA enrichment
  3. 2026-07-26 22:49 UTCEG score recompute
  4. 2026-07-26 22:48 UTCGHSA enrichment
  5. 2026-07-26 14:51 UTCEPSS rescore
  6. 2026-07-25 14:14 UTCEPSS rescore
  7. 2026-07-24 14:14 UTCEPSS rescore
  8. 2026-07-24 14:14 UTCEPSS rescore
  9. 2026-07-23 14:15 UTCEPSS rescore
  10. 2026-07-23 01:44 UTCEG score recompute
  11. 2026-07-22 22:25 UTCEG score recompute
  12. 2026-07-22 14:05 UTCEPSS rescore
  13. 2026-07-21 15:22 UTCEPSS rescore
  14. 2026-07-21 15:22 UTCEPSS rescore
  15. 2026-07-20 17:04 UTCEPSS rescore
  16. 2026-07-20 17:04 UTCEPSS rescore
  17. 2026-07-19 14:28 UTCEPSS rescore
  18. 2026-07-19 14:28 UTCEPSS rescore
  19. 2026-07-19 02:26 UTCEPSS rescore
  20. 2026-07-19 02:26 UTCEPSS rescore
  21. 2026-07-18 10:01 UTCEPSS rescore
  22. 2026-07-16 16:59 UTCEPSS rescore
  23. 2026-07-16 16:59 UTCEPSS rescore
  24. 2026-07-16 00:55 UTCGHSA enrichment
  25. 2026-07-15 16:55 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 16:55 UTCEPSS rescore
  2. 2026-07-14 03:36 UTCGHSA enrichment
  3. 2026-07-13 22:27 UTCEPSS rescore
  4. 2026-07-13 06:10 UTCEPSS rescore
  5. 2026-07-13 06:10 UTCEPSS rescore
  6. 2026-07-12 05:43 UTCEPSS rescore
  7. 2026-07-12 05:43 UTCEPSS rescore
  8. 2026-07-11 12:52 UTCGHSA enrichment
  9. 2026-07-11 08:24 UTCEPSS rescore
  10. 2026-07-11 08:24 UTCEPSS rescore
  11. 2026-07-09 19:06 UTCEPSS rescore
  12. 2026-07-08 16:34 UTCGHSA enrichment
  13. 2026-07-08 15:11 UTCEPSS rescore
  14. 2026-07-07 13:43 UTCEPSS rescore
  15. 2026-07-06 16:25 UTCEPSS rescore
  16. 2026-07-06 16:25 UTCEPSS rescore
  17. 2026-07-06 02:20 UTCEPSS rescore
  18. 2026-07-05 02:27 UTCEPSS rescore
  19. 2026-07-04 06:28 UTCEPSS rescore
  20. 2026-07-03 22:18 UTCGHSA enrichment
  21. 2026-07-02 02:56 UTCGHSA enrichment
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-07-01 15:03 UTCEPSS rescore
  24. 2026-07-01 02:22 UTCGHSA enrichment
  25. 2026-06-30 23:20 UTCEPSS rescore
  26. 2026-06-30 01:47 UTCGHSA enrichment
  27. 2026-06-29 14:03 UTCEPSS rescore
  28. 2026-06-29 01:13 UTCGHSA enrichment
  29. 2026-06-28 14:04 UTCEPSS rescore
  30. 2026-06-28 04:54 UTCEPSS rescore
  31. 2026-06-28 04:54 UTCEPSS rescore
  32. 2026-06-28 00:38 UTCGHSA enrichment
  33. 2026-06-27 03:06 UTCEPSS rescore
  34. 2026-06-27 00:00 UTCGHSA enrichment
  35. 2026-06-25 23:01 UTCGHSA enrichment
  36. 2026-06-25 13:47 UTCEPSS rescore
  37. 2026-06-25 13:47 UTCEPSS rescore
  38. 2026-06-24 22:27 UTCGHSA enrichment
  39. 2026-06-24 14:03 UTCEPSS rescore
  40. 2026-06-24 14:03 UTCEPSS rescore
  41. 2026-06-23 21:31 UTCEPSS rescore
  42. 2026-06-23 21:30 UTCEPSS rescore
  43. 2026-06-23 19:30 UTCGHSA enrichment
  44. 2026-06-22 14:23 UTCEPSS rescore
  45. 2026-06-21 14:54 UTCEPSS rescore
  46. 2026-06-21 14:54 UTCEPSS rescore
  47. 2026-06-21 01:57 UTCEPSS rescore
  48. 2026-06-21 01:57 UTCEPSS rescore
  49. 2026-06-19 23:59 UTCGHSA enrichment
  50. 2026-06-19 19:23 UTCEPSS rescore
  51. 2026-06-19 19:23 UTCEPSS rescore
  52. 2026-06-18 17:50 UTCEPSS rescore
  53. 2026-06-18 04:17 UTCGHSA enrichment
  54. 2026-06-17 17:50 UTCEPSS rescore
  55. 2026-06-17 03:43 UTCGHSA enrichment
  56. 2026-06-16 17:50 UTCEPSS rescore
  57. 2026-06-16 03:09 UTCGHSA enrichment
  58. 2026-06-15 17:45 UTCEPSS rescore
  59. 2026-06-15 02:34 UTCGHSA enrichment
  60. 2026-06-14 23:15 UTCEPSS rescore
  61. 2026-06-14 23:15 UTCEPSS rescore
  62. 2026-06-14 02:00 UTCGHSA enrichment
  63. 2026-06-13 22:58 UTCEPSS rescore
  64. 2026-06-13 01:26 UTCGHSA enrichment
  65. 2026-06-12 23:09 UTCEPSS rescore
  66. 2026-06-12 00:52 UTCGHSA enrichment
  67. 2026-06-11 13:58 UTCEPSS rescore
  68. 2026-06-11 00:18 UTCGHSA enrichment
  69. 2026-06-10 22:16 UTCEPSS rescore
  70. 2026-06-10 13:19 UTCEPSS rescore
  71. 2026-06-09 23:44 UTCGHSA enrichment
  72. 2026-06-08 23:11 UTCGHSA enrichment
  73. 2026-06-08 14:15 UTCEPSS rescore
  74. 2026-06-07 22:37 UTCGHSA enrichment
  75. 2026-06-07 15:23 UTCEPSS rescore

Frequently asked(5)

What is CVE-2019-25724?
CVE-2019-25724 is a medium vulnerability published on June 2, 2026. Dräger Infinity M300 patient worn monitors with software version VG2.x and earlier contain a network-based denial of service vulnerability that allows attackers with access to the hospital or Infinity Network to repeatedly trigger device reboots until the device enters a fail state requiring manual…
When was CVE-2019-25724 disclosed?
CVE-2019-25724 was first published in the National Vulnerability Database on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-25724 actively exploited?
CVE-2019-25724 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.8% of all scored CVEs.
What is the CVSS score of CVE-2019-25724?
CVE-2019-25724 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2019-25724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25724, 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-25724

Explore →

Is Your Infrastructure Affected by CVE-2019-25724?

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