Skip to content
Fencer Vulns
medium 6.8

CVE-2025-4395 json

Medtronic MyCareLink Patient Monitor Empty Password Vulnerability

published 2025-07-24 15 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-22480

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

Medtronic MyCareLink Patient Monitor has a built-in user account with an empty password, which allows an attacker with physical access to log in with no password and access modify system functionality.

This issue affects MyCareLink Patient Monitor models 24950 and 24952: before June 25, 2025

Patch / fix

  • Medtronic MyCareLink Patient Monitor 24950 June 25, 2025
  • Medtronic MyCareLink Patient Monitor 24952 June 25, 2025

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-25-205-01 updated cvss 6.8

Medtronic MyCareLink Patient Monitor (Update A)

  • Medtronic MyCareLink Patient Monitor model 24950 Medtronic MyCareLink Patient Monitor model 24952
    affected: mitigation “Medtronic recommends the following actions:” medtronic.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
15 mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Medtronic MyCareLink Patient Monitor 24950
  • Medtronic MyCareLink Patient Monitor 24952

Classification

Weakness
  • CWE-258 Empty Password in Configuration File

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.