CVE-2019-25722

HIGHPre-NVD 7.67.6
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.6Exploit: NoneExposed: 0

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

Dräger SC Monitoring devices (SC 6002XL, SC 6802XL, SC 7000, SC 8000, SC 9000 XL) contain hard-coded plaintext credentials in source code and a denial-of-service vulnerability that allows local and remote attackers to compromise device integrity across all software versions. A local attacker with direct device access can use the hard-coded credentials to access service and clinical accounts and alter device configuration, while a remote attacker can send malformed network packets to cause repeated device reboots, ultimately resulting in loss of network connectivity and disruption of patient monitoring.

CVSS v3
7.6
EG Score
7.6(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
9.2%
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Vendor Advisories for CVE-2019-25722(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 15× in last 7d / 72× 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 137 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2019-25722?
CVE-2019-25722 is a high vulnerability published on June 2, 2026. Dräger SC Monitoring devices (SC 6002XL, SC 6802XL, SC 7000, SC 8000, SC 9000 XL) contain hard-coded plaintext credentials in source code and a denial-of-service vulnerability that allows local and remote attackers to compromise device integrity across all software versions. A local attacker with…
When was CVE-2019-25722 disclosed?
CVE-2019-25722 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-25722 actively exploited?
CVE-2019-25722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-25722?
CVE-2019-25722 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2019-25722?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-25722, 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-25722

Explore →

Is Your Infrastructure Affected by CVE-2019-25722?

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